Triple
T8844107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Querétaro International Airport |
E210460
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | QRO |
E186164
|
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: QRO | Statement: [Querétaro International Airport, IATAcode, QRO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: QRO Context triple: [Querétaro International Airport, IATAcode, QRO]
-
A.
QRO
chosen
QRO is the vehicle registration code used on license plates for the Mexican state of Querétaro.
-
B.
QOR
QOR is the abbreviation commonly used for The Queen's Own Rifles of Canada, a historic primary reserve infantry regiment of the Canadian Army.
-
C.
QF
QF is the IATA airline designator used for Qantas, the flag carrier of Australia.
-
D.
QRL
QRL is the Queensland Rugby League, the governing body responsible for administering and promoting rugby league in Queensland, Australia.
-
E.
QH
QH is the standard abbreviation for Qinghai, a large inland province in northwestern China known for the Qinghai-Tibet Plateau and Qinghai Lake.
- 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc608a73c88190875409fef79ffc8a |
completed | April 1, 2026, 12:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf89ad0a3c8190a2bcf9a106138835 |
completed | April 3, 2026, 9:34 a.m. |
Created at: March 30, 2026, 6:48 p.m.