Triple
T2512085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonia Exhipódromo de Peralvillo |
E52723
|
entity |
| Predicate | streetAddressSystem |
P1216
|
FINISHED |
| Object | Mexico City addressing system |
—
|
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: Mexico City addressing system | Statement: [Colonia Exhipódromo de Peralvillo, streetAddressSystem, Mexico City addressing system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetAddressSystem Context triple: [Colonia Exhipódromo de Peralvillo, streetAddressSystem, Mexico City addressing system]
-
A.
usesAddressingSystem
chosen
Indicates that one entity employs or applies a particular addressing system associated with another entity.
-
B.
streetAddress
Indicates the specific location of an entity in terms of its numbered building and street name within a postal address.
-
C.
postalCodeSystem
Indicates a system that assigns structured postal codes to geographic areas for organizing and routing mail.
-
D.
streetAddressRange
Indicates the span of street address numbers (e.g., from a minimum to a maximum) that are associated with a particular street segment or location.
-
E.
streetLocation
Indicates that one entity is located on, along, or at a specific street associated with the other 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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0bf37c0819088d28b5081ba7556 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.