Triple
T35758170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosworth DFV engine |
E1033501
|
entity |
| Predicate | firstWinningDriver |
P99785
|
FINISHED |
| Object | Jim Clark |
E1348003
|
NE 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: Jim Clark | Statement: [Cosworth DFV engine, firstWinningDriver, Jim Clark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstWinningDriver Context triple: [Cosworth DFV engine, firstWinningDriver, Jim Clark]
-
A.
firstWinningDrivers
Indicates the relationship where certain drivers are the first to achieve a race victory within a given context (such as a series, season, team, or event).
-
B.
firstFormulaOneWin
chosen
Indicates that the subject achieved their first victory in a Formula One race in relation to the specified event or context.
-
C.
firstPolePositionDriver
Indicates the driver who achieved the very first pole position in a given racing event or series.
-
D.
grandPrixWin
Indicates that an entity has achieved victory in a Grand Prix event or race.
-
E.
driversChampionshipWin
Indicates that a driver has won the overall drivers’ championship title in a given racing series or season.
- F. None of above.
Provenance (4 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38915a6bd081908d6638afde1a31f7 |
completed | June 22, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.