Triple
T13714367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosío |
E328854
|
entity |
| Predicate | ISO3166-2Code |
P208
|
FINISHED |
| Object | MX-AGU |
E1058111
|
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-AGU | Statement: [Cosío, ISO3166-2Code, MX-AGU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MX-AGU Context triple: [Cosío, ISO3166-2Code, MX-AGU]
-
A.
MX-AGU
chosen
MX-AGU is the ISO 3166-2 subdivision code assigned to the Mexican state of Aguascalientes.
-
B.
MX-COL
MX-COL is the ISO 3166-2 subdivision code assigned to the municipality of Colima in the Mexican state of Colima.
-
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.
ROCI Mexico
ROCI Mexico was the Mexican installment of Robert Rauschenberg’s global Rauschenberg Overseas Culture Interchange project, featuring site-specific works and cultural exchange activities created and exhibited in Mexico.
-
E.
Maxtla
Maxtla was a Tepanec ruler of Azcapotzalco in pre-Columbian central Mexico, known for his aggressive expansionism and conflict with neighboring city-states such as Tenochtitlan.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd43973cf08190a417d0cca9dd314a |
completed | April 13, 2026, 7:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7a847c4d08190b05ea525059f0465 |
completed | May 3, 2026, 7:55 p.m. |
Created at: April 9, 2026, 9:54 p.m.