Triple
T35752557
| 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 | pointsForFirstPlace |
P24875
|
FINISHED |
| Object | 25 |
—
|
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: 25 | Statement: [FIA Formula One 25–18–15–12–10–8–6–4–2–1 scoring system, pointsForFirstPlace, 25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsForFirstPlace Context triple: [FIA Formula One 25–18–15–12–10–8–6–4–2–1 scoring system, pointsForFirstPlace, 25]
-
A.
pointsAwarded
Indicates that a specified number of points has been granted to an entity as a result of some action or event.
-
B.
tieForFirstPlace
Indicates that two or more competitors share the highest rank or score, resulting in no single clear winner.
-
C.
pointsForWin
chosen
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
D.
pointsLeader
Indicates that the subject entity is the current leader in points relative to other entities in a given context or competition.
-
E.
winnerPoints
Indicates the number of points earned by the winning participant or entity in a competition or event.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.