Triple
T27514365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microcentro |
E694502
|
entity |
| Predicate | typicalStreetType |
P44319
|
FINISHED |
| Object | narrow street |
—
|
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: narrow street | Statement: [Microcentro, typicalStreetType, narrow street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStreetType Context triple: [Microcentro, typicalStreetType, narrow street]
-
A.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
B.
isCommonStreetNameIn
Indicates that a given name is frequently used as a street name within a specified geographic area or jurisdiction.
-
C.
streetOrAreaType
chosen
Indicates the specific kind or classification of a street or area (such as avenue, boulevard, district, or zone) associated with an entity.
-
D.
correspondsToStreetType
Indicates that one entity matches or is associated with a particular type or classification of street.
-
E.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ffbe9e47688190a2692566dc326646 |
completed | May 9, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69ffbb7b45388190b62cbde5c2d435cd |
completed | May 9, 2026, 10:55 p.m. |
Created at: April 27, 2026, 1:18 p.m.