Triple
T7405636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State of Guerrero |
E170861
|
entity |
| Predicate | ISO3166-2 |
P189
|
FINISHED |
| Object | MX-GRO |
E170864
|
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-GRO | Statement: [State of Guerrero, ISO3166-2, MX-GRO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MX-GRO Context triple: [State of Guerrero, ISO3166-2, MX-GRO]
-
A.
MX-GRO
chosen
MX-GRO is the ISO 3166-2 regional code for the Mexican state of Guerrero, where the city of Acapulco is located.
-
B.
MX-ROO
MX-ROO is the ISO 3166-2 subdivision code assigned to the Mexican state of Quintana Roo.
-
C.
MZG
MZG is the vehicle registration code used on license plates for vehicles registered in the town of Wadern in Germany.
-
D.
MZG
MZG is the IATA airport code for Penghu Airport, which serves the Penghu (Pescadores) archipelago in Taiwan.
-
E.
MGY
MGY was the distinctive wireless call sign used by the RMS Titanic for its radio communications.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f271f1d481909a46d50b13b51a62 |
completed | March 27, 2026, 9:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8111540f08190919bc9d9670f5ef2 |
completed | March 28, 2026, 5:34 p.m. |
Created at: March 27, 2026, 3:10 p.m.