Triple
T20763764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coll Airport |
E511039
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | COL |
—
|
NE NERFINISHED |
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: COL | Statement: [Coll Airport, IATA code, COL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: COL Context triple: [Coll Airport, IATA code, COL]
-
A.
COL
COL is the standard three-letter abbreviation used for the Colorado Rockies Major League Baseball team.
-
B.
COL
COL is the standard three-letter abbreviation used to represent the Colorado Rapids, a professional Major League Soccer team based in the Denver metropolitan area.
-
C.
COL
COL is the acronym for the Commonwealth of Learning, an intergovernmental organization that promotes open and distance learning across Commonwealth countries.
-
D.
COL
chosen
COL is the three-letter IATA airport code assigned to Coll Airport, a small airfield serving the island of Coll in Scotland.
-
E.
COL
COL is the three-letter FIFA country code used to represent the Colombia national football team in international competitions and rankings.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24b18b8819082e61104be6f83a3 |
completed | April 21, 2026, 12:18 a.m. |
Created at: April 16, 2026, 12:35 p.m.