Triple
T37671316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonia San Pedro de los Pinos |
E937964
|
entity |
| Predicate | streetGridType |
P12506
|
FINISHED |
| Object | orthogonal grid |
—
|
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: orthogonal grid | Statement: [Colonia San Pedro de los Pinos, streetGridType, orthogonal grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetGridType Context triple: [Colonia San Pedro de los Pinos, streetGridType, orthogonal grid]
-
A.
streetGridExtendedFrom
Indicates that one street grid layout continues or expands outward from another street grid as its extension.
-
B.
streetGridOrientation
Indicates the predominant directional alignment or pattern of streets within a given area or city layout.
-
C.
streetGridRange
Indicates the span or extent of a street segment within a defined grid or block range in a street network.
-
D.
hasStreetGridFeature
Indicates that a location or area possesses a specific characteristic or element of a street grid layout, such as a particular pattern, structure, or feature of its road network.
-
E.
hasStreetGridPattern
chosen
Indicates that an area’s street layout follows a structured, grid-like pattern of intersecting roads.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.