Triple
T8184012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McMinnville Municipal Airport |
E191136
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | MMV |
E716782
|
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: MMV | Statement: [McMinnville Municipal Airport, FAA LID, MMV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MMV Context triple: [McMinnville Municipal Airport, FAA LID, MMV]
-
A.
MMV
chosen
MMV is the three-letter IATA airport code for McMinnville Municipal Airport in McMinnville, Oregon, United States.
-
B.
MM
MM is a post-nominal abbreviation indicating that a person has been awarded the Military Medal for bravery in battle.
-
C.
MMZ
MMZ is the ICAO airline designator assigned to EuroAtlantic Airways, a Portuguese charter and wet-lease carrier.
-
D.
MMM
MMM is a post-nominal designation signifying membership in the Order of Military Merit, a Canadian honor recognizing exceptional service and devotion by members of the Canadian Armed Forces.
-
E.
KMMV
KMMV is the ICAO airport code for McMinnville Municipal Airport, a public airport serving McMinnville in Yamhill County, Oregon, United States.
- 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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4f4ef88190ad346edad14b67ee |
completed | March 31, 2026, 4:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cced6fd33081909512adbe559b2c7a |
completed | April 1, 2026, 10:03 a.m. |
Created at: March 30, 2026, 5:41 p.m.