Triple
T8808564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Metropolitan Airport |
E209596
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | CAE |
E759489
|
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: CAE | Statement: [Columbia Metropolitan Airport, FAAcode, CAE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CAE Context triple: [Columbia Metropolitan Airport, FAAcode, CAE]
-
A.
CAE
CAE (Computer-Aided Engineering) is the use of computer software to simulate, analyze, and optimize engineering designs and processes.
-
B.
CAE
chosen
CAE is the IATA airport code for Columbia Metropolitan Airport, the primary commercial airport serving Columbia, South Carolina.
-
C.
CAE
CAE is a Canadian multinational company specializing in simulation and training solutions, particularly for civil aviation, defense, and healthcare industries.
-
D.
CAEATFA
CAEATFA is a California state agency that provides financing support to promote alternative energy, energy efficiency, and advanced transportation technologies.
-
E.
CAI
CAI is the three-letter IATA airport code for Cairo International Airport, the main international gateway to Cairo, Egypt.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fd4cbec8190a929d4e60da8ad65 |
completed | March 31, 2026, 11:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf892b813481909739f72ffd080f49 |
completed | April 3, 2026, 9:32 a.m. |
Created at: March 30, 2026, 6:45 p.m.