Triple
T35894829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosworth HB engine |
E1038189
|
entity |
| Predicate | introducedAtGrandPrix |
P8259
|
FINISHED |
| Object | 1989 French Grand Prix |
—
|
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: 1989 French Grand Prix | Statement: [Cosworth HB engine, introducedAtGrandPrix, 1989 French Grand Prix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAtGrandPrix Context triple: [Cosworth HB engine, introducedAtGrandPrix, 1989 French Grand Prix]
-
A.
introducedGrandPrixLocation
Indicates that an entity initiated or brought a particular Grand Prix event to a specific location for the first time.
-
B.
grandPrixDebutYear
Indicates the year in which an entity first participated in a Grand Prix event.
-
C.
introducedDuring
chosen
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
-
D.
racingSeriesDebut
Indicates the event or point in time at which an entity first participates in a particular racing series.
-
E.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 3, 2026, 4:06 p.m.