Triple
T8935836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McComb-Pike County Airport |
E212772
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | MCB |
E767046
|
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: MCB | Statement: [McComb-Pike County Airport, FAA LID, MCB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MCB Context triple: [McComb-Pike County Airport, FAA LID, MCB]
-
A.
MCB
chosen
MCB is the IATA airport code for McComb-Pike County Airport, a public airport serving the McComb area in Mississippi, United States.
-
B.
MCBH
MCBH is a major United States Marine Corps installation located on the island of Oahu in Hawaii, supporting Marine, Navy, and joint military operations in the Pacific region.
-
C.
MCV
MCV is the National Rail station code for Manchester Victoria railway station, a major rail hub in Manchester, England.
-
D.
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.
-
E.
MCD
MCD is the FAA location identifier for Mackinac Island Airport, a small public airport serving Mackinac Island in Michigan, USA.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66928cec8190915636d663f843af |
completed | April 1, 2026, 12:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc937ded08190a67fd4457b6458ff |
completed | April 3, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:58 p.m.