Triple
T4126128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacDill Air Force Base |
E92728
|
entity |
| Predicate | hasFAAIdentifier |
P420
|
FINISHED |
| Object | MCF |
E414949
|
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: MCF | Statement: [MacDill Air Force Base, hasFAAIdentifier, MCF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MCF Context triple: [MacDill Air Force Base, hasFAAIdentifier, MCF]
-
A.
MCF
chosen
MCF is the IATA airport code for the military airfield serving MacDill Air Force Base in Tampa, Florida.
-
B.
MCD
MCD is a system of urban and suburban commuter rail lines in Moscow designed to function like an express metro, connecting the city with its surrounding regions.
-
C.
KMCF
KMCF is the ICAO airport code for the military airfield serving MacDill Air Force Base in Tampa, Florida.
-
D.
MfS
MfS was the official state security and intelligence service of the former East Germany, widely known for its extensive surveillance and repression of the population.
-
E.
Mc
Mc is a Gaelic patronymic prefix meaning "son of," commonly found in Scottish and Irish surnames.
- 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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69af0219f0e48190b0a925f09d858d65 |
completed | March 9, 2026, 5:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b57f256abc819086cd464be1a9efbf |
completed | March 14, 2026, 3:30 p.m. |
Created at: March 9, 2026, 3:41 p.m.