Triple
T7023762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorado Springs Airport |
E162891
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | COS |
E636779
|
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: COS | Statement: [Colorado Springs Airport, FAAcode, COS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: COS Context triple: [Colorado Springs Airport, FAAcode, COS]
-
A.
COS
chosen
COS is the IATA airport code for Colorado Springs Airport, a commercial airport serving Colorado Springs, Colorado, in the United States.
-
B.
COS
COS is the French Armed Forces' elite joint command responsible for planning and conducting special operations.
-
C.
COS
COS is the College of Science at Northeastern University, encompassing disciplines such as biology, chemistry, physics, mathematics, and related scientific fields.
-
D.
COS
COS is a Hubble Space Telescope instrument designed to study the origins and evolution of the universe by analyzing the ultraviolet light from distant astronomical objects.
-
E.
CLO
CLO is the acronym for the Conselh de la Lenga Occitana, the official body responsible for regulating and standardizing the Occitan language.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e1fa043c81909c900e394a5972f9 |
completed | March 27, 2026, 8 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c78857d23c8190904a90459a802cb8 |
completed | March 28, 2026, 7:50 a.m. |
Created at: March 27, 2026, 2:35 p.m.