Triple
T755743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mojave Air and Space Port |
E15550
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | KMHV |
E15550
|
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: KMHV | Statement: [Mojave Air and Space Port, ICAO code, KMHV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KMHV Context triple: [Mojave Air and Space Port, ICAO code, KMHV]
-
A.
MHV
chosen
MHV is the IATA airport code for Mojave Air and Space Port, a well-known aerospace testing and flight facility in Mojave, California.
-
B.
Mvezo
Mvezo is a small rural village in South Africa’s Eastern Cape best known as the birthplace of Nelson Mandela.
-
C.
KGH
KGH is the National Rail station code for Kinghorn railway station in Fife, Scotland.
-
D.
KIX
KIX is the three-letter IATA airport code for Kansai International Airport serving the Osaka region of Japan.
-
E.
Hama
Hama is a major city in west-central Syria, historically known for its ancient waterwheels (norias) on the Orontes River and its role as an important agricultural and industrial center.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6693cbc8190a167e12a896d7ce7 |
completed | March 1, 2026, 8:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a66673d6288190bb6a68c6c376016e |
completed | March 3, 2026, 4:41 a.m. |
Created at: March 1, 2026, 7:37 p.m.