Triple
T26190407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prahran railway station |
E654945
|
entity |
| Predicate | isInInnerSuburbsOf |
P52341
|
FINISHED |
| Object | Melbourne |
—
|
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: Melbourne | Statement: [Prahran railway station, isInInnerSuburbsOf, Melbourne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInInnerSuburbsOf Context triple: [Prahran railway station, isInInnerSuburbsOf, Melbourne]
-
A.
isInnerRingSuburb
chosen
Indicates that a suburb is located within the inner ring of a city, typically close to the central business district and developed in the earlier phases of urban expansion.
-
B.
isOuterSuburbOf
Indicates that one place is a suburban area located on the outer edge or periphery of another, typically larger, urban area.
-
C.
isInSuburbanArea
Indicates that something is located within a suburban area, typically between urban and rural regions.
-
D.
innerSuburbOf
Indicates that one location is a suburb situated within or forming part of a larger city or metropolitan area.
-
E.
isResidentialSuburbOf
Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60ca177ac81908b2bfd6b7c0f93e3 |
completed | May 2, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:44 p.m.