Triple
T34549759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Código Postal de México |
E887028
|
entity |
| Predicate | hasMappingTo |
P33157
|
FINISHED |
| Object | INEGI geographic divisions |
E744742
|
NE 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: INEGI geographic divisions | Statement: [Código Postal de México, hasMappingTo, INEGI geographic divisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMappingTo Context triple: [Código Postal de México, hasMappingTo, INEGI geographic divisions]
-
A.
hasMappingProperty
chosen
Indicates that there exists a defined correspondence or association between elements of one set, structure, or representation and elements of another.
-
B.
hasOfficialMapping
Indicates that there exists an established, authoritative correspondence or translation between one entity and another.
-
C.
hasCanonicalMapFrom
Indicates that there exists a standard or uniquely determined structure-preserving map from one entity to another.
-
D.
hasMapReference
Indicates that an entity is associated with a specific map or map location reference.
-
E.
hasMapBy
Indicates that one entity is represented, depicted, or detailed by a specific map associated with it.
- F. None of above.
Provenance (4 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a01b31b233c819091974a06f7a76d4a |
completed | May 11, 2026, 10:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3729f7395c8190824c42c8b7f8972c |
completed | June 21, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a01b2c147008190bbf9e0fa1bbae1f3 |
completed | May 11, 2026, 10:43 a.m. |
Created at: May 1, 2026, 2:02 a.m.