Triple
T13476955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Drivers' Championship |
E318273
|
entity |
| Predicate | historicalNameInUseUntil |
P25649
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [World Drivers' Championship, historicalNameInUseUntil, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalNameInUseUntil Context triple: [World Drivers' Championship, historicalNameInUseUntil, 1980s]
-
A.
usedAsTownNameUntil
Indicates that an entity served as the official or common name of a town up to a specified point in time.
-
B.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
-
C.
previousNameUsedUntil
chosen
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
D.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
-
E.
operatedAsNameUntil
Indicates that an entity functioned or was known under a particular name up to a specified point in time.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf2551b48190a074fd256791742d |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.