Triple
T7118161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Bulldogs Football Club |
E165871
|
entity |
| Predicate | notablePremiership |
P74667
|
FINISHED |
| Object | 2016 drought-breaking flag |
—
|
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: 2016 drought-breaking flag | Statement: [Western Bulldogs Football Club, notablePremiership, 2016 drought-breaking flag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePremiership Context triple: [Western Bulldogs Football Club, notablePremiership, 2016 drought-breaking flag]
-
A.
notablePremiershipYears
Indicates the years during which an entity held a notable or distinguished premiership (term as prime minister or equivalent head of government).
-
B.
premiershipCount
Indicates the number of premiership titles or championships an entity has won.
-
C.
notableLeague
Indicates that there is a significant or prominent league associated with the subject entity.
-
D.
premiershipYearAsPlayer
Indicates the year in which an individual participated as a player on a team that won a premiership or championship title.
-
E.
notableClub
Indicates that an entity is prominently associated with or recognized for membership in a particular club or organization.
- 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_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. |
| PDg | Predicate description generation | batch_69c6e456e89481908df42a1b4232a4a0 |
completed | March 27, 2026, 8:11 p.m. |
Created at: March 27, 2026, 2:43 p.m.