Triple
T33545980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nurzhol Boulevard |
E859206
|
entity |
| Predicate | urbanPlanRole |
P14108
|
FINISHED |
| Object | main axis of Astana’s Left Bank development |
—
|
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: main axis of Astana’s Left Bank development | Statement: [Nurzhol Boulevard, urbanPlanRole, main axis of Astana’s Left Bank development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanPlanRole Context triple: [Nurzhol Boulevard, urbanPlanRole, main axis of Astana’s Left Bank development]
-
A.
roleInUrbanPlan
chosen
Indicates the specific function, responsibility, or position an entity holds within an urban planning context or scheme.
-
B.
urbanRole
Indicates the function, status, or role that an entity holds within an urban or city context.
-
C.
urbanPolicyRole
Indicates a role or responsibility that an entity has in shaping, implementing, or influencing urban policy.
-
D.
urbanPlanningFunction
Indicates a functional role or purpose that something serves within the planning, organization, or management of urban spaces and infrastructure.
-
E.
urbanPlanBy
Indicates that an urban plan is created, designed, or authored by a specific agent or authority.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:39 a.m.