Triple
T32885369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Kilda Football Club |
E841183
|
entity |
| Predicate | representedSuburb |
P180698
|
FINISHED |
| Object | St Kilda |
—
|
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: St Kilda | Statement: [St Kilda Football Club, representedSuburb, St Kilda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedSuburb Context triple: [St Kilda Football Club, representedSuburb, St Kilda]
-
A.
representsSuburb
chosen
Indicates that one entity serves as the official or recognized suburb associated with another entity, such as a city, region, or address.
-
B.
locatedInSuburbType
Indicates that one entity is situated within, or belongs to, a specific type or category of suburb associated with the other entity.
-
C.
innerSuburbOf
Indicates that one location is a suburb situated within or forming part of a larger city or metropolitan area.
-
D.
isResidentialSuburbOf
Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
-
E.
associatedWithSuburb
Indicates a relationship where something is linked or connected to a particular suburb, such as being located in, serving, or otherwise related to that suburb.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:18 a.m.