Triple
T22287367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Touring Car Championship |
E550897
|
entity |
| Predicate | secondEraStart |
P17325
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [World Touring Car Championship, secondEraStart, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondEraStart Context triple: [World Touring Car Championship, secondEraStart, 2005]
-
A.
secondGenerationStartYear
chosen
Indicates the calendar year in which the second generation of something (e.g., a product, model, or series) begins.
-
B.
secondEditionStartDate
Indicates the date on which the second edition of something officially begins or is first released.
-
C.
secondPeriodName
Indicates the name or label assigned to the second period in an ordered sequence of time intervals or stages.
-
D.
secondCreationYear
Indicates the year in which an entity was created for the second time, such as after being recreated, relaunched, or re-established.
-
E.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560896348190985725ac8ad406b3 |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.