Triple
T24897760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Street, Melbourne |
E623190
|
entity |
| Predicate | isWithinPlanningArea |
P39182
|
FINISHED |
| Object | Melbourne CBD planning zone |
—
|
LITERAL 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: Melbourne CBD planning zone | Statement: [Queen Street, Melbourne, isWithinPlanningArea, Melbourne CBD planning zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWithinPlanningArea Context triple: [Queen Street, Melbourne, isWithinPlanningArea, Melbourne CBD planning zone]
-
A.
isInArea
chosen
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
B.
hasUrbanPlanningZone
Indicates that an area or property is designated as belonging to a specific urban planning zone within a planning or zoning scheme.
-
C.
isInProtectedArea
Indicates that an entity is located within a designated protected or conservation area.
-
D.
partOfPlanningRegion
Indicates that one entity is included within, or belongs to, a larger designated planning region.
-
E.
plannedArea
Indicates that an area is designated or intended for a specific planned use or development.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 5:26 a.m.