Triple
T17725898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 2 (Frankfurt Airport) |
E442459
|
entity |
| Predicate | connectedTo |
P37
|
FINISHED |
| Object | Terminal 1 (Frankfurt Airport) |
—
|
NE NERFINISHED |
How this triple was built (3 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: Terminal 1 (Frankfurt Airport) | Statement: [Terminal 2 (Frankfurt Airport), connectedTo, Terminal 1 (Frankfurt Airport)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Terminal 1 (Frankfurt Airport) Context triple: [Terminal 2 (Frankfurt Airport), connectedTo, Terminal 1 (Frankfurt Airport)]
-
A.
Terminal 1 (Hamburg Airport)
Terminal 1 at Hamburg Airport is a modern passenger terminal handling check-in, security, and boarding operations for various airlines at the international airport serving Hamburg, Germany.
-
B.
Terminal 1 of Berlin Brandenburg Airport
Terminal 1 of Berlin Brandenburg Airport is the airport’s main passenger terminal, housing the primary check-in, security, and boarding facilities for most airlines and flights.
-
C.
Terminal 2 of Berlin Brandenburg Airport
Terminal 2 of Berlin Brandenburg Airport is a passenger terminal facility designed to handle additional low-cost and leisure airline traffic alongside the airport’s main Terminal 1 complex.
-
D.
Terminal 5 of Berlin Brandenburg Airport
Terminal 5 of Berlin Brandenburg Airport is the former Berlin Schönefeld Airport terminal complex, used as an additional low-cost and regional passenger facility for the new Berlin Brandenburg Airport.
-
E.
Frankfurt Airport
Frankfurt Airport is one of Europe’s busiest international aviation hubs, serving as a major global gateway and primary airport for the city of Frankfurt am Main in Germany.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Terminal 1 (Frankfurt Airport) Target entity description: Terminal 1 at Frankfurt Airport is the airport’s largest and oldest terminal, serving as a major hub for Lufthansa and Star Alliance carriers with extensive international and domestic flight operations.
-
A.
Terminal 1 (Hamburg Airport)
Terminal 1 at Hamburg Airport is a modern passenger terminal handling check-in, security, and boarding operations for various airlines at the international airport serving Hamburg, Germany.
-
B.
Terminal 1 of Berlin Brandenburg Airport
Terminal 1 of Berlin Brandenburg Airport is the airport’s main passenger terminal, housing the primary check-in, security, and boarding facilities for most airlines and flights.
-
C.
Terminal 2 of Berlin Brandenburg Airport
Terminal 2 of Berlin Brandenburg Airport is a passenger terminal facility designed to handle additional low-cost and leisure airline traffic alongside the airport’s main Terminal 1 complex.
-
D.
Terminal 5 of Berlin Brandenburg Airport
Terminal 5 of Berlin Brandenburg Airport is the former Berlin Schönefeld Airport terminal complex, used as an additional low-cost and regional passenger facility for the new Berlin Brandenburg Airport.
-
E.
Frankfurt Airport
Frankfurt Airport is one of Europe’s busiest international aviation hubs, serving as a major global gateway and primary airport for the city of Frankfurt am Main in Germany.
- F. None of above. chosen
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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47489c59c8190bbffefad20dc6346 |
completed | April 19, 2026, 6:22 a.m. |
Created at: April 10, 2026, 10:07 a.m.