Triple
T14368512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estado Libre y Soberano de México |
E356294
|
entity |
| Predicate | hasUNLOCODE |
P1492
|
FINISHED |
| Object | MX-MEX |
E43362
|
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: MX-MEX | Statement: [Estado Libre y Soberano de México, hasUNLOCODE, MX-MEX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MX-MEX Context triple: [Estado Libre y Soberano de México, hasUNLOCODE, MX-MEX]
-
A.
MEX
MEX is a major expressway in Malaysia that connects Kuala Lumpur to Putrajaya and Cyberjaya, helping to ease traffic congestion between the capital and its southern suburbs.
-
B.
MEX
chosen
MEX is the IATA airport code for Mexico City International Airport, the main international gateway serving Mexico City and one of the busiest airports in Latin America.
-
C.
G-Mex
G-Mex is the former name of the Manchester Central Convention Complex, a major exhibition and events venue in Manchester, England.
-
D.
MX-AGU
MX-AGU is the ISO 3166-2 subdivision code assigned to the Mexican state of Aguascalientes.
-
E.
MX-COL
MX-COL is the ISO 3166-2 subdivision code assigned to the municipality of Colima in the Mexican state of Colima.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8fb0b8988190ab834a85911c015c |
completed | April 14, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c51bf888190b1776461884c4514 |
completed | May 8, 2026, 2:37 a.m. |
Created at: April 10, 2026, 1:15 a.m.