Triple
T1546628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Cristóbal de La Laguna |
E32991
|
entity |
| Predicate | urbanPlanType |
P8653
|
FINISHED |
| Object | grid plan |
—
|
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: grid plan | Statement: [San Cristóbal de La Laguna, urbanPlanType, grid plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanPlanType Context triple: [San Cristóbal de La Laguna, urbanPlanType, grid plan]
-
A.
urbanPlanningFunction
Indicates a functional role or purpose that something serves within the planning, organization, or management of urban spaces and infrastructure.
-
B.
urbanDevelopmentType
Indicates the specific category or nature of urban development associated with or applied to an entity (e.g., residential, commercial, mixed-use).
-
C.
urbanPlanInspiredBy
Indicates that an urban planning design, strategy, or project is conceptually derived from, modeled on, or significantly influenced by another plan, precedent, or source.
-
D.
urbanPlanningStyle
Indicates the characteristic approach or methodology used in planning and organizing urban spaces and development.
-
E.
planType
chosen
Indicates the specific category or kind of plan associated with an entity, such as its level, structure, or intended 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_69a885ed29088190a3c2d5a3d100c16e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa574094048190a2d7fc3ac904d51e |
completed | March 6, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69a907b426dc8190975c024a50955368 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.