Triple
T35752592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 Formula One season |
E1033355
|
entity |
| Predicate | championConstructor |
P184048
|
FINISHED |
| Object | Mercedes |
—
|
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: Mercedes | Statement: [2017 Formula One season, championConstructor, Mercedes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championConstructor Context triple: [2017 Formula One season, championConstructor, Mercedes]
-
A.
championOf
Indicates that one entity serves as the primary defender, advocate, or leading supporter of another entity, often working to promote or protect its interests.
-
B.
championManager
Indicates that one entity serves as the manager, coach, or primary overseer responsible for the success or performance of a champion entity.
-
C.
champion
Indicates that one entity has won a competition or contest and holds the top position or title over others.
-
D.
championOwner
Indicates that one entity is the owner or holder of a championship title associated with another entity.
-
E.
championCarMake
chosen
Indicates that a particular car make is the champion or winning make in a given context, such as a race, season, or competition.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:06 p.m.