Triple
T6600225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCO |
E148977
|
entity |
| Predicate | icaoCodeFor |
P419
|
FINISHED |
| Object | KMCO |
E148978
|
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: KMCO | Statement: [MCO, icaoCodeFor, KMCO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KMCO Context triple: [MCO, icaoCodeFor, KMCO]
-
A.
KMCO
chosen
KMCO is the ICAO airport code for Orlando International Airport, a major commercial airport serving the Orlando, Florida metropolitan area.
-
B.
KCO
KCO is the abbreviated name commonly used for the Royal Concertgebouw Orchestra, one of the world’s leading symphony orchestras based in Amsterdam.
-
C.
KMC
KMC is the municipal governing body responsible for providing and managing civic services and infrastructure in Karachi, Pakistan.
-
D.
KMC
KMC is the commonly used abbreviation for Kirori Mal College, a prominent constituent college of the University of Delhi in India.
-
E.
KMCE
KMCE is the ICAO airport code for Merced Regional Airport, a public airport serving Merced, California.
- 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_69c687eaa7508190bb58ce2aa02039b3 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6aef36b308190a172f0396e337309 |
completed | March 27, 2026, 4:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6e434afd08190807faf0069c70cce |
completed | March 27, 2026, 8:10 p.m. |
Created at: March 27, 2026, 1:56 p.m.