Triple
T33045149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1967 Formula One World Championship |
E845573
|
entity |
| Predicate | constructorsChampionEngine |
P110542
|
FINISHED |
| Object | Repco |
—
|
NE NERFINISHED |
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: Repco | Statement: [1967 Formula One World Championship, constructorsChampionEngine, Repco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructorsChampionEngine Context triple: [1967 Formula One World Championship, constructorsChampionEngine, Repco]
-
A.
engineConstructor
chosen
Indicates that an entity is the manufacturer or builder responsible for constructing a particular engine.
-
B.
engineClass
Indicates the classification or type category assigned to an engine within a given system or context.
-
C.
chassisDesigner
Indicates that one entity is the designer or creator responsible for the chassis of another entity.
-
D.
manufacturerChampion
Indicates that a manufacturer actively promotes, supports, or advocates for a particular entity, product, or initiative as a key champion.
-
E.
engineComponent
Indicates that one entity functions as a component or part of an engine in relation to another 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 1, 2026, 1:24 a.m.