Triple
T25445066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandringham Football Club |
E637610
|
entity |
| Predicate | hasWonPremiershipIn |
P101445
|
FINISHED |
| Object | Victorian Football League |
—
|
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: Victorian Football League | Statement: [Sandringham Football Club, hasWonPremiershipIn, Victorian Football League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWonPremiershipIn Context triple: [Sandringham Football Club, hasWonPremiershipIn, Victorian Football League]
-
A.
wonPremiershipIn
chosen
Indicates that an entity secured victory in a premiership competition in a specified year or season.
-
B.
wonPremiershipWith
Indicates that an entity achieved a premiership title while being a member of or associated with a particular team, club, or organization.
-
C.
premiershipWonYear
Indicates the specific year in which an entity won a premiership title.
-
D.
premiershipCount
Indicates the number of premiership titles or championships an entity has won.
-
E.
wonPremierLeague
Indicates that the subject has achieved victory in the Premier League competition for at least one season.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 21, 2026, 2 p.m.