Triple
T7117919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1934 VFL premiership |
E165865
|
entity |
| Predicate | grandFinalLosingScore |
P7493
|
FINISHED |
| Object | 12.17 (89) |
—
|
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: 12.17 (89) | Statement: [1934 VFL premiership, grandFinalLosingScore, 12.17 (89)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grandFinalLosingScore Context triple: [1934 VFL premiership, grandFinalLosingScore, 12.17 (89)]
-
A.
loserScore
chosen
Indicates the number of points or score achieved by the losing participant in a competitive event or comparison.
-
B.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
C.
finalBoutLoser
Indicates that an entity is the competitor who lost in the final bout of a match, tournament, or competition.
-
D.
opponentFinalScore
Indicates the final score achieved by an opposing participant or team in a contest or game.
-
E.
pointsScoredByLosingTeam
Indicates the number of points scored by the team that did not win in a given game or match.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e618bdac8190be291468b7d977bb |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.