Triple
T5462981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge City Airport |
E122637
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | EGSC |
E122637
|
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: EGSC | Statement: [Cambridge City Airport, ICAOCode, EGSC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EGSC Context triple: [Cambridge City Airport, ICAOCode, EGSC]
-
A.
EGSC
chosen
EGSC is the ICAO airport code for Cambridge City Airport in Cambridge, England.
-
B.
GSC
GSC is the commonly used abbreviation for the General Secretariat of the Council of the European Union, the administrative body that supports the Council’s work and decision-making processes.
-
C.
GSC
GSC is the Geological Survey of Canada, the national scientific agency responsible for studying and mapping Canada’s geology, natural resources, and geological hazards.
-
D.
ESGP
ESGP is the ICAO airport code for Gothenburg City Airport, a regional airport serving the Gothenburg area in Sweden.
-
E.
EGSS
EGSS is the ICAO airport code assigned to London Stansted Airport, a major international airport serving the London area in the United Kingdom.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd92033dd08190a90bcae6b9f149d3 |
completed | March 20, 2026, 6:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf488866088190b213bd641f8b247c |
completed | March 22, 2026, 1:40 a.m. |
Created at: March 20, 2026, 2:08 p.m.