Triple
T36034702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-AMG Petronas Formula One Team |
E1042364
|
entity |
| Predicate | enteredFormulaOneAsConstructor |
P82780
|
FINISHED |
| Object | 2010 |
—
|
LITERAL 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: 2010 | Statement: [Mercedes-AMG Petronas Formula One Team, enteredFormulaOneAsConstructor, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredFormulaOneAsConstructor Context triple: [Mercedes-AMG Petronas Formula One Team, enteredFormulaOneAsConstructor, 2010]
-
A.
enteredFormulaOne
chosen
Indicates that an entity began competing in Formula One racing, marking its entry into the Formula One championship.
-
B.
firstFormulaOneGrandPrix
Indicates the event at which an entity made its debut participation in a Formula One Grand Prix.
-
C.
firstFormulaOneTeam
Indicates the Formula One team for which an entity (typically a driver) first competed.
-
D.
premierClassOf
Indicates that one entity is the top or highest-level class or category to which another entity belongs.
-
E.
firstFormulaOneWin
Indicates that the subject achieved their first victory in a Formula One race in relation to the specified event or context.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:07 p.m.