Triple
T21513144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U1 |
E530776
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object | Hallesches Tor |
E72035
|
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: Hallesches Tor | Statement: [U1, hasStation, Hallesches Tor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hallesches Tor Context triple: [U1, hasStation, Hallesches Tor]
-
A.
Hallesches Tor
chosen
Hallesches Tor is a major Berlin U-Bahn interchange station in the Kreuzberg district, serving as a key hub for multiple subway lines.
-
B.
Frankfurter Tor
Frankfurter Tor is a prominent square and transport hub in Berlin’s Friedrichshain district, notable for its twin-towered Stalinist architecture and role as a gateway to the city’s historic Karl-Marx-Allee.
-
C.
Eschenheimer Tor
Eschenheimer Tor is a historic city gate and prominent landmark in central Frankfurt am Main, Germany.
-
D.
Tübinger Tor
Tübinger Tor is a historic city gate and notable architectural landmark in Reutlingen, Germany.
-
E.
Berliner Tor
Berliner Tor is a historic city gate in Wesel, Germany, notable for its baroque architecture and role in the town’s former fortifications.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea8779c081908171c58d345d54ae |
completed | April 23, 2026, 9:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a09eed3e4e881908cae748e38845a6e |
completed | May 17, 2026, 4:37 p.m. |
Created at: April 16, 2026, 6:25 p.m.