Triple
T34265984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Kilda Junction |
E879166
|
entity |
| Predicate | adjacentLocalGovernmentArea |
P115982
|
FINISHED |
| Object | City of Port Phillip |
—
|
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: City of Port Phillip | Statement: [St Kilda Junction, adjacentLocalGovernmentArea, City of Port Phillip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentLocalGovernmentArea Context triple: [St Kilda Junction, adjacentLocalGovernmentArea, City of Port Phillip]
-
A.
hasNeighboringLGA
chosen
Indicates that one local government area is geographically adjacent to or directly borders another local government area.
-
B.
servedLocalGovernmentArea
Indicates that an entity has provided official service, representation, or duties within a specified local government area.
-
C.
localGovernmentAreaOf
Indicates that one entity is the local government area within whose jurisdiction or administrative boundaries the other entity is located.
-
D.
neighboringBarangay
Indicates that two barangays are directly adjacent to each other, sharing a common boundary or border.
-
E.
neighbouringMunicipality
Indicates that one municipality directly borders and is adjacent to another municipality.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 1:56 a.m.