Triple
T17381819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durham Tees Valley Airport |
E422586
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | MME |
—
|
NE NERFINISHED |
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: MME | Statement: [Durham Tees Valley Airport, IATAcode, MME]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MME Context triple: [Durham Tees Valley Airport, IATAcode, MME]
-
A.
MME
chosen
MME is the IATA airport code for Teesside International Airport, serving the Teesside and County Durham region in northeast England.
-
B.
Mobility Management Entity
The Mobility Management Entity is a core LTE network component responsible for user mobility, session management, and signaling control between user devices and the network.
-
C.
M2M
M2M is a Norwegian pop duo best known for their late-1990s and early-2000s teen pop hits like "Don't Say You Love Me."
-
D.
MMEP
MMEP is the ICAO airport code for Tepic International Airport in Tepic, Nayarit, Mexico.
-
E.
MMI
MMI is an abbreviation for Muslim Mosque, Inc., a religious organization associated with the Muslim community.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a86d8cc81909281b22f5da87d70 |
completed | April 19, 2026, 2:14 a.m. |
Created at: April 10, 2026, 5:45 a.m.