Triple
T7153036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BA CityFlyer |
E166739
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | CFE |
E611253
|
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: CFE | Statement: [BA CityFlyer, ICAOcode, CFE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CFE Context triple: [BA CityFlyer, ICAOcode, CFE]
-
A.
CFE
chosen
CFE is the IATA airport code for Clermont-Ferrand Auvergne Airport in central France.
-
B.
CEF
CEF is the abbreviation for the Canadian Expeditionary Force, the field force of the Canadian Army raised for service overseas during the First World War.
-
C.
CFC
CFC is the abbreviation commonly used for the Combined Forces Command, a joint military headquarters coordinating combined operations.
-
D.
CFC
CFC is a leading Canadian institution dedicated to advancing the careers of filmmakers, screenwriters, and other media creators through professional training and development programs.
-
E.
CFC
CFC is a common abbreviation for the Collingwood Football Club, a professional Australian rules football team in the Australian Football League.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f52c1081908c4fa424d5e965bc |
completed | March 27, 2026, 8:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7adb0ea288190b7eef76de30a3a1e |
completed | March 28, 2026, 10:30 a.m. |
Created at: March 27, 2026, 2:46 p.m.