Triple
T3381297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U6 |
E71188
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object | Tempelhof |
E72452
|
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: Tempelhof | Statement: [U6, hasStation, Tempelhof]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tempelhof Context triple: [U6, hasStation, Tempelhof]
-
A.
Tempelhof Airport
Tempelhof Airport is a historic Berlin airfield best known as a central hub of the Berlin Airlift during the Cold War.
-
B.
Tegel
Tegel is a locality in the Reinickendorf borough of Berlin, Germany, historically known for its manor associated with the Humboldt family and later for the former Berlin Tegel Airport.
-
C.
Alt-Tempelhof
chosen
Alt-Tempelhof is an underground station on Berlin’s U-Bahn network serving the Tempelhof district in the southern part of the city.
-
D.
Spandau
Spandau is a western borough of Berlin, Germany, known for its historic old town, fortress, and role as an important residential and industrial district.
-
E.
Schönefeld
Schönefeld is a municipality just southeast of Berlin in the German state of Brandenburg, known for hosting the Berlin Brandenburg Airport.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5e9af608190bfb228ef99a87bb7 |
completed | March 8, 2026, 5:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b35462c69481909700f01bacdac3e1 |
completed | March 13, 2026, 12:03 a.m. |
Created at: March 8, 2026, 3:14 p.m.