Triple
T27564279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geelong Football Club |
E695853
|
entity |
| Predicate | hasHomeGroundNameHistory |
P118171
|
FINISHED |
| Object | Kardinia Park |
—
|
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: Kardinia Park | Statement: [Geelong Football Club, hasHomeGroundNameHistory, Kardinia Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeGroundNameHistory Context triple: [Geelong Football Club, hasHomeGroundNameHistory, Kardinia Park]
-
A.
homeGroundNameHistory
chosen
Indicates the historical sequence of names that have been used for an entity’s home ground or home venue over time.
-
B.
previousHomeGroundLocatedIn
Indicates that the location specified is where an entity’s former or earlier home ground was situated.
-
C.
denotesHomeGroundOf
Indicates that a particular location serves as the primary home ground or home venue for a specified team, organization, or entity.
-
D.
hasHomeCountryLeague
Indicates that an entity (typically a sports team or player) is associated with a specific league that operates in its home country.
-
E.
hasHomeRegionHistorical
Indicates that an entity is historically associated with or originates from a particular home region.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 27, 2026, 1:40 p.m.