Triple
T35795461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Australian Grand Prix |
E1034817
|
entity |
| Predicate | championshipPointsForWinner |
P7114
|
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: [2016 Australian Grand Prix, championshipPointsForWinner, 25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championshipPointsForWinner Context triple: [2016 Australian Grand Prix, championshipPointsForWinner, 25]
-
A.
championshipOutcome
Indicates the result or final standing of a competitor or team in a championship event.
-
B.
includesChampionshipPoints
Indicates that the referenced item contains or accounts for championship points as part of its data or outcome.
-
C.
totalPointsByChampionInFinal
Indicates the total number of points scored by a given champion in the final match or round.
-
D.
winnerPoints
chosen
Indicates the number of points earned by the winning participant or entity in a competition or event.
-
E.
rankingPointsSinglesChampion
Indicates the number of ranking points awarded to an entity for winning a singles championship.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:06 p.m.