Triple
T34992832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Melbourne/Sydney Swans |
E1009440
|
entity |
| Predicate | originalHomeSuburb |
P206786
|
FINISHED |
| Object | South Melbourne |
E879167
|
NE 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: South Melbourne | Statement: [South Melbourne/Sydney Swans, originalHomeSuburb, South Melbourne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalHomeSuburb Context triple: [South Melbourne/Sydney Swans, originalHomeSuburb, South Melbourne]
-
A.
originalSuburbBase
Indicates that one location serves as the original or primary suburban area from which another related suburb or suburban entity is derived or defined.
-
B.
isResidentialSuburbOf
Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
-
C.
innerSuburbOf
Indicates that one location is a suburb situated within or forming part of a larger city or metropolitan area.
-
D.
locatedInSuburbType
Indicates that one entity is situated within, or belongs to, a specific type or category of suburb associated with the other entity.
-
E.
suburb
Indicates that one place is a residential district or outlying area that is part of or adjacent to a larger city or town.
- F. None of above. chosen
Provenance (5 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b28b75e48190848542bd083179d8 |
completed | June 21, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.