Triple
T10957898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Midlands Airport |
E258892
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | EMA |
E258891
|
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: EMA | Statement: [East Midlands Airport, IATACode, EMA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EMA Context triple: [East Midlands Airport, IATACode, EMA]
-
A.
EMA
EMA is the European Union’s regulatory authority responsible for the scientific evaluation, supervision, and safety monitoring of medicines.
-
B.
EMA
chosen
EMA is the three-letter IATA airport code for East Midlands Airport in England, which serves the East Midlands region with domestic and international flights.
-
C.
EMA
EMA is the abbreviated name for the Joint Staff headquarters that oversees and coordinates the operations of the French Armed Forces.
-
D.
EMA
EMA is the acronym for the Spanish Navy Staff, the central command body responsible for directing and managing Spain’s naval forces.
-
E.
Em
Em is a common shortened form of the given name Emma, often used as an informal nickname.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77126d9288190aa5daf2ba83d731d |
completed | April 9, 2026, 9:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3447d8cc88190a3e28f204a93a7d3 |
completed | April 18, 2026, 8:44 a.m. |
Created at: April 8, 2026, 9:23 p.m.