Triple
T15842890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adrian Sutil |
E384139
|
entity |
| Predicate | careerPointsInFormulaOne |
P103570
|
FINISHED |
| Object | 124 |
—
|
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: 124 | Statement: [Adrian Sutil, careerPointsInFormulaOne, 124]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: careerPointsInFormulaOne Context triple: [Adrian Sutil, careerPointsInFormulaOne, 124]
-
A.
F1Points
chosen
Indicates that an entity has earned or is associated with a specific number of Formula 1 championship points.
-
B.
careerPoints
Indicates the total number of points an individual has accumulated over the course of their entire career in a given activity or domain.
-
C.
numberOfF1WorldChampionships
Indicates the number of Formula 1 World Championship titles that an entity has won.
-
D.
totalFormulaOnePodiums
Indicates the total number of times an entity has finished on the podium (top three positions) in Formula One races.
-
E.
totalPolePositions
Indicates the total number of times an entity has achieved pole position in qualifying or starting order across all relevant events.
- 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_69d86da34c888190976e06c4019d415a |
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.