Triple
T35752562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIA Formula One 25–18–15–12–10–8–6–4–2–1 scoring system |
E1033354
|
entity |
| Predicate | pointsForSixthPlace |
P185360
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [FIA Formula One 25–18–15–12–10–8–6–4–2–1 scoring system, pointsForSixthPlace, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsForSixthPlace Context triple: [FIA Formula One 25–18–15–12–10–8–6–4–2–1 scoring system, pointsForSixthPlace, 8]
-
A.
sixthPlace
Indicates that an entity holds the sixth position or rank in an ordered sequence, competition, or arrangement.
-
B.
pointsForFifthPlace
Indicates the number of points awarded to an entity for finishing in fifth place in a ranking or competition.
-
C.
pointsForFourthPlace
Indicates the number of points awarded to an entity for finishing in fourth place in a ranking or competition.
-
D.
pointsForThirdPlace
Indicates the number of points awarded to an entity for finishing in third place in a ranking or competition.
-
E.
runnersUpPoints
Indicates the number of points awarded to an entity for finishing as a runner-up in a competition or ranking.
- F. None of above. chosen
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_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: May 3, 2026, 4:06 p.m.