Triple
T30142340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Performance Car of the Year 2008 |
E766161
|
entity |
| Predicate | vehicleModelYearApprox |
P4161
|
FINISHED |
| Object | around 2008 |
—
|
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: around 2008 | Statement: [World Performance Car of the Year 2008, vehicleModelYearApprox, around 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleModelYearApprox Context triple: [World Performance Car of the Year 2008, vehicleModelYearApprox, around 2008]
-
A.
conceptCarYear
Indicates the year in which a concept car was first introduced, presented, or designated.
-
B.
modelYears
chosen
Indicates the association between a product (often a vehicle or device) and the specific calendar years in which that model version was produced or marketed.
-
C.
vehicleModelProduced
Indicates that a particular vehicle model is manufactured or produced by a specific company or producer.
-
D.
yearDeliveredApprox
Indicates that the year an item or entity was delivered is known only approximately, rather than as an exact calendar year.
-
E.
winnerModelYear
Indicates that a model was the winning model for a particular year.
- F. None of above.
Provenance (3 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e88c0ec8190b9d5e62d482f6deb |
completed | May 2, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:18 p.m.