Triple
T6213236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otis Air Force Base |
E138920
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | FMH |
E575711
|
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: FMH | Statement: [Otis Air Force Base, FAAcode, FMH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FMH Context triple: [Otis Air Force Base, FAAcode, FMH]
-
A.
FMH
chosen
FMH is the IATA airport code for Otis Air National Guard Base, a military airfield located in Massachusetts, United States.
-
B.
FAM
FAM is the acronym commonly used to refer to the Mexican Air Force, the aerial warfare branch of Mexico’s armed forces.
-
C.
FMF
FMF is the commonly used abbreviation for the Mexican Football Federation, the governing body of professional and amateur soccer in Mexico.
-
D.
FHU
FHU is the national governing body responsible for overseeing and developing ice hockey in Ukraine.
-
E.
FHU
FHU is the IATA airport code for Libby Army Airfield, a joint-use military and civilian airport serving the Fort Huachuca area in Arizona, 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_69c008ada364819096c9e92c74d639b5 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0628c52ec8190b9c62c7fdc0aa83b |
completed | March 22, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c20da55e3c81909a61471b38e88894 |
completed | March 24, 2026, 4:05 a.m. |
Created at: March 22, 2026, 4:21 p.m.