Triple
T7813654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 5 (Berlin Brandenburg Airport) |
E180746
|
entity |
| Predicate | IATAAirportServed |
P418
|
FINISHED |
| Object | BER |
E71200
|
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: BER | Statement: [Terminal 5 (Berlin Brandenburg Airport), IATAAirportServed, BER]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BER Context triple: [Terminal 5 (Berlin Brandenburg Airport), IATAAirportServed, BER]
-
A.
BER
chosen
BER is Berlin Brandenburg Airport, the main international airport serving Germany’s capital region.
-
B.
BER
BER is the ICAO airline designator formerly used by the now-defunct German carrier Air Berlin.
-
C.
BER
BER is a U.S. Department of Energy research program that advances fundamental science on biological systems and environmental processes to address energy and climate challenges.
-
D.
BEL
BEL is the ICAO airline designator used to identify Brussels Airlines in international aviation operations.
-
E.
BEL
BEL is the commonly used abbreviation for Bharat Electronics Limited, an Indian state-owned aerospace and defense electronics company.
- 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_69ca827f6f148190beca4e245b993506 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78f3d6481909841d64117f657e1 |
completed | March 30, 2026, 10:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc55e579e081909f5036dd33d64e38 |
completed | March 31, 2026, 11:16 p.m. |
Created at: March 30, 2026, 4:38 p.m.