Triple
T11619715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Pleasant Municipal Airport |
E275605
|
entity |
| Predicate | FAAIdentifier |
P420
|
FINISHED |
| Object | MOP |
E938080
|
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: MOP | Statement: [Mount Pleasant Municipal Airport, FAAIdentifier, MOP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MOP Context triple: [Mount Pleasant Municipal Airport, FAAIdentifier, MOP]
-
A.
MOP
MOP is the ISO 4217 currency code for the Macanese pataca, the official currency of Macau.
-
B.
MOP
chosen
MOP is the IATA airport code for Mount Pleasant Municipal Airport in Michigan, United States.
-
C.
MOPITT
MOPITT is a satellite instrument aboard NASA's Terra spacecraft designed to measure global distributions of atmospheric carbon monoxide and methane for climate and air quality research.
-
D.
JMO
JMO is the IATA airport code for Jomsom Airport, a domestic airport serving the town of Jomsom in Nepal’s Mustang region.
-
E.
IMO
IMO is a specialized United Nations agency responsible for regulating international shipping and promoting maritime safety, security, and environmental protection.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a1206f1c81908d92024ef71958c0 |
completed | April 10, 2026, 7:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef1330cfc0819086a07139b6c82c10 |
completed | April 27, 2026, 7:41 a.m. |
Created at: April 8, 2026, 9:38 p.m.