Triple
T34217539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District 11 of Zürich |
E877834
|
entity |
| Predicate | urbanPlanningArea |
P60867
|
FINISHED |
| Object | Zürich Nord |
—
|
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: Zürich Nord | Statement: [District 11 of Zürich, urbanPlanningArea, Zürich Nord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanPlanningArea Context triple: [District 11 of Zürich, urbanPlanningArea, Zürich Nord]
-
A.
urbanPlanningFunction
Indicates a functional role or purpose that something serves within the planning, organization, or management of urban spaces and infrastructure.
-
B.
plannedArea
chosen
Indicates that an area is designated or intended for a specific planned use or development.
-
C.
urbanPlanBy
Indicates that an urban plan is created, designed, or authored by a specific agent or authority.
-
D.
urbanPlanningForm
Indicates the specific type or structure of urban planning approach applied to a place or development.
-
E.
urbanPlanningBody
Indicates that an entity serves as an official organization responsible for planning, regulating, or managing urban development and land use.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:55 a.m.