Triple
T35752571
| 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 | winnerToThirdGap |
P189368
|
FINISHED |
| Object | 10 points |
—
|
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: 10 points | Statement: [FIA Formula One 25–18–15–12–10–8–6–4–2–1 scoring system, winnerToThirdGap, 10 points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerToThirdGap Context triple: [FIA Formula One 25–18–15–12–10–8–6–4–2–1 scoring system, winnerToThirdGap, 10 points]
-
A.
pointsForThirdPlace
Indicates the number of points awarded to an entity for finishing in third place in a ranking or competition.
-
B.
lapsLedByWinner
Indicates the number of laps in a race that were led by the eventual winner.
-
C.
stageReachedByWinner
Indicates the competition stage that the eventual winner had reached or achieved.
-
D.
winnerToSecondRatio
Indicates the proportional relationship between the winner’s value (e.g., score, time, or performance measure) and that of the second-place entity.
-
E.
winnerRound
Indicates that an entity is the one who won a particular round in a multi-round event or competition.
- 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_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:06 p.m.