Triple
T3115462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet Express (facelifted variants) |
E65051
|
entity |
| Predicate | offeredConfiguration |
P45418
|
FINISHED |
| Object | 1500 series |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1500 series | Statement: [Chevrolet Express (facelifted variants), offeredConfiguration, 1500 series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredConfiguration Context triple: [Chevrolet Express (facelifted variants), offeredConfiguration, 1500 series]
-
A.
associatedOffering
Indicates a relationship where one offering is linked or connected to another offering as related or contextually relevant.
-
B.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
-
C.
offeredService
Indicates that one entity has provided or made available a service to another entity.
-
D.
offeredEngineType
Indicates that a particular type of engine is made available or provided as an option in a given context.
-
E.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to another entity.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada4e40bc48190b9b17c706a2450d5 |
completed | March 8, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.