Triple
T38473299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ANZ Championship |
E915477
|
entity |
| Predicate | finalSeasonChampions |
P197726
|
FINISHED |
| Object | Queensland Firebirds |
—
|
NE NERFINISHED |
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: Queensland Firebirds | Statement: [ANZ Championship, finalSeasonChampions, Queensland Firebirds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalSeasonChampions Context triple: [ANZ Championship, finalSeasonChampions, Queensland Firebirds]
-
A.
finalChampions
Indicates that the related entities are the ultimate winners or title holders at the conclusion of a competition, season, or tournament.
-
B.
notableFinalSeasonChampion
chosen
Indicates that the subject is notably recognized as the champion in the final season of a competition, series, or event.
-
C.
lastSeasonChampion
Indicates that the subject is the champion or winner of the immediately preceding season of the relevant competition or event.
-
D.
seasonChampion
Indicates that an entity is the winner or champion of a particular season of a competition, league, or series.
-
E.
firstSeasonChampions
Indicates that the subject entity won the championship in the first season of the relevant competition or series.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.