Triple
T2603940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Channel Express |
E58611
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | EXS |
E58609
|
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: EXS | Statement: [Channel Express, ICAOcode, EXS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EXS Context triple: [Channel Express, ICAOcode, EXS]
-
A.
EXS
chosen
EXS is the ICAO airline designator used for Jet2.com, a British low-cost leisure airline based in the United Kingdom.
-
B.
ES-EX
ES-EX is the ISO 3166-2 subdivision code that uniquely identifies the autonomous community of Extremadura within Spain.
-
C.
Exos
Exos is Seagate Technology’s high-capacity enterprise hard drive product line designed for data centers and large-scale storage environments.
-
D.
HESX
HESX is the ICAO airport code assigned to Sphinx International Airport in Egypt.
-
E.
EXPE
EXPE is the stock ticker symbol for Expedia Group, a major American online travel company that operates brands like Expedia.com, Hotels.com, and Vrbo.
- 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8340eac819084eb1fe6f0ac0aa0 |
completed | March 7, 2026, 7:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af907ebc348190b1556a2104cba6f1 |
completed | March 10, 2026, 3:31 a.m. |
Created at: March 6, 2026, 9:49 p.m.