Triple
T25476691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essendon Football Club |
E638451
|
entity |
| Predicate | homeStateLeagueHistory |
P159450
|
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: [Essendon Football Club, homeStateLeagueHistory, Victorian Football League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStateLeagueHistory Context triple: [Essendon Football Club, homeStateLeagueHistory, Victorian Football League]
-
A.
homeStateLeagueRegion
Indicates the geographic league region that corresponds to an entity’s home state.
-
B.
homeStateTeam
Indicates that a sports team is based in, or represents, the home state of a given person or entity.
-
C.
homeStateTeamOf
Indicates that one team is the designated home-state team associated with a particular person, organization, or region.
-
D.
homeStateFanBase
Indicates that a fan base is primarily located in or strongly associated with the same state as the team, person, or entity it supports.
-
E.
playsForProvinceOrState
Indicates that an athlete or player is a member of, or represents, a particular provincial or state-level team 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7555c688190b28c0de18902fdbe |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 21, 2026, 2:26 p.m.