Triple
T7117921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1934 VFL premiership |
E165865
|
entity |
| Predicate | premiershipNumberForWinner |
P16341
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [1934 VFL premiership, premiershipNumberForWinner, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiershipNumberForWinner Context triple: [1934 VFL premiership, premiershipNumberForWinner, 4]
-
A.
premiershipCount
chosen
Indicates the number of premiership titles or championships an entity has won.
-
B.
secondPremiershipYear
Indicates the year in which an entity held or achieved its second term of premiership.
-
C.
captainedPremiershipYear
Indicates the year in which an entity served as captain of a team in a premiership (championship) competition.
-
D.
numberOfPremierDivisions
Indicates the count of premier divisions associated with or attributed to an entity.
-
E.
premiershipYearAsPlayer
Indicates the year in which an individual participated as a player on a team that won a premiership or championship title.
- 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.