Triple
T20185450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte Vista Municipal Airport |
E492843
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | MVI |
—
|
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: MVI | Statement: [Monte Vista Municipal Airport, FAA LID, MVI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MVI Context triple: [Monte Vista Municipal Airport, FAA LID, MVI]
-
A.
MVI
chosen
MVI is the IATA airport code for Monte Vista Municipal Airport, a public airport serving Monte Vista in Colorado, United States.
-
B.
MIV
MIV is a specialized market segment of Borsa Italiana dedicated to the listing and trading of investment vehicles such as closed-end funds and investment companies.
-
C.
MIVB
MIVB is the Dutch acronym for Brussels’ main public transport operator, which runs the city’s metro, tram, and bus networks.
-
D.
MVY
MVY is the IATA airport code for Martha's Vineyard Airport, the primary commercial airport serving Martha's Vineyard in Massachusetts, USA.
-
E.
BMVI
BMVI is the abbreviation for Germany’s former Federal Ministry responsible for transport policy and digital infrastructure development.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668f2c03c819096336462f59dba91 |
completed | April 20, 2026, 5:57 p.m. |
Created at: April 11, 2026, 11:36 p.m.