Triple
T33842796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexandria, Sydney |
E867398
|
entity |
| Predicate | planningZoning |
P143311
|
FINISHED |
| Object | mixed-use |
—
|
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: mixed-use | Statement: [Alexandria, Sydney, planningZoning, mixed-use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningZoning Context triple: [Alexandria, Sydney, planningZoning, mixed-use]
-
A.
landUsePlanning
chosen
Indicates the relationship in which an authority or agent organizes, regulates, or designates how land and space may be used or developed within a given area.
-
B.
zoningAuthority
Indicates that an entity has official power or jurisdiction to regulate land use and development within a specified area.
-
C.
urbanPlanApproved
Indicates that an official authority has reviewed and formally authorized a proposed urban development or land-use plan.
-
D.
urbanPlanningForm
Indicates the specific type or structure of urban planning approach applied to a place or development.
-
E.
cityPlanningDesignation
Indicates how an area is officially classified or designated within urban or municipal planning (e.g., residential, commercial, industrial).
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:47 a.m.