Triple
T8423511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Nicolás neighborhood |
E198918
|
entity |
| Predicate | streetTypeDominant |
P44319
|
FINISHED |
| Object | mixed commercial and office streets |
—
|
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: mixed commercial and office streets | Statement: [San Nicolás neighborhood, streetTypeDominant, mixed commercial and office streets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetTypeDominant Context triple: [San Nicolás neighborhood, streetTypeDominant, mixed commercial and office streets]
-
A.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
B.
roadName
Indicates the specific name assigned to a road that identifies it within a transportation or address system.
-
C.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
D.
streetOrientedAlong
Indicates that a street is aligned or runs in the same general direction as a specified reference feature or axis.
-
E.
streetOrAreaType
chosen
Indicates the specific kind or classification of a street or area (such as avenue, boulevard, district, or zone) associated with an entity.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb859f787481908a11797a317c8849 |
completed | March 31, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.