Triple
T138482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mojave Air and Space Port |
E2799
|
entity |
| Predicate | FAAIdentifier |
P420
|
FINISHED |
| Object | MHV |
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: MHV | Statement: [Mojave Air and Space Port, FAAIdentifier, MHV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MHV Context triple: [Mojave Air and Space Port, FAAIdentifier, MHV]
-
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.
MCV
MCV is the National Rail station code for Manchester Victoria railway station, a major rail hub in Manchester, England.
-
C.
MX
MX is the two-letter ISO 3166-1 alpha-2 country code that uniquely identifies Mexico in international standards and systems.
-
D.
HARV
HARV is the standard abbreviation used for the Harvard Crimson men's basketball team in collegiate athletics contexts.
-
E.
MC
MC is the official abbreviation for NATO’s highest military authority, the NATO Military Committee.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a800148190be119d1d075869b8 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a2b85fe4d481909e39b745857b62e7 |
completed | Feb. 28, 2026, 9:41 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.