Triple
T30216647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonia Santa Cruz Atoyac |
E768222
|
entity |
| Predicate | postalCodeLocatedIn |
P920
|
FINISHED |
| Object | Mexico City postal code 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 postal code system | Statement: [Colonia Santa Cruz Atoyac, postalCodeLocatedIn, Mexico City postal code system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalCodeLocatedIn Context triple: [Colonia Santa Cruz Atoyac, postalCodeLocatedIn, Mexico City postal code system]
-
A.
postalName
Indicates the standardized name or label used for addressing and postal purposes associated with an entity.
-
B.
postalArea
chosen
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
-
C.
postalCode
Indicates the numerical or alphanumerical code assigned to a geographic area for mail delivery associated with an entity.
-
D.
postalCodeInCountry
Indicates that a given postal code is assigned to and valid within a particular country.
-
E.
postalCodeCenter
Indicates the central geographic point or representative location associated with a given postal code area.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff62f088190bee521030fe98284 |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:34 p.m.