Triple
T35751984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Drivers’ Championship |
E1033341
|
entity |
| Predicate | notableConstructorInvolved |
P44379
|
FINISHED |
| Object | Mercedes-Benz |
E11202
|
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: Mercedes-Benz | Statement: [European Drivers’ Championship, notableConstructorInvolved, Mercedes-Benz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableConstructorInvolved Context triple: [European Drivers’ Championship, notableConstructorInvolved, Mercedes-Benz]
-
A.
notableConstructor
chosen
Indicates that an entity is a well-known or significant creator, builder, or originator of another entity.
-
B.
notableFormerConstructor
Indicates that an entity was previously a constructor (e.g., team or organization) associated with another entity in a way considered notable or significant.
-
C.
notableMethod
Indicates that a particular method, technique, or approach is especially significant, recognized, or noteworthy in relation to the associated entity.
-
D.
notableExecutionMethod
Indicates that a particular method or manner of execution is especially notable or characteristic in relation to the subject.
-
E.
usedConstructor
Indicates that one entity instantiated or created another entity by invoking a specific constructor.
- 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_6a3885e79e788190add7887e2fefb7c7 |
completed | June 22, 2026, 12:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.