Triple
T13476954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Drivers' Championship |
E318273
|
entity |
| Predicate | historicalNameInUseFrom |
P2834
|
FINISHED |
| Object | 1950 |
—
|
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: 1950 | Statement: [World Drivers' Championship, historicalNameInUseFrom, 1950]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalNameInUseFrom Context triple: [World Drivers' Championship, historicalNameInUseFrom, 1950]
-
A.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
-
B.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
-
C.
historicallyBorneBy
chosen
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
D.
historicallyRecognizedAs
Indicates that an entity has been acknowledged or designated under a particular name, status, or role during a past historical period.
-
E.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or 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.