Triple
T15843186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midland F1 Racing |
E384147
|
entity |
| Predicate | firstSeasonInFormulaOne |
P56687
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Midland F1 Racing, firstSeasonInFormulaOne, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSeasonInFormulaOne Context triple: [Midland F1 Racing, firstSeasonInFormulaOne, 2006]
-
A.
debutInFormulaOneSeason
chosen
Indicates the Formula One season during which an entity (typically a driver or team) made its first official appearance in the championship.
-
B.
ageAtFirstFormulaOneWin
Indicates the age a person was when they achieved their first Formula One race victory.
-
C.
firstFormulaOneWin
Indicates that the subject achieved their first victory in a Formula One race in relation to the specified event or context.
-
D.
enteredFormulaOne
Indicates that an entity began competing in Formula One racing, marking its entry into the Formula One championship.
-
E.
racingDebut
Indicates the event or moment when an entity first participates in an official race or competitive racing activity.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142ea3da08190a9d2d5917f84907c |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005434ed88190baf11c169da3cf29 |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.