Triple
T20132754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jüterbog |
E490937
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object |
Dammtor city gate
The Dammtor city gate is a historic medieval gate in Jüterbog, Germany, that once formed part of the town’s defensive fortifications.
|
E1413701
|
NE FINISHED |
How this triple was built (4 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: Dammtor city gate | Statement: [Jüterbog, hasLandmark, Dammtor city gate]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dammtor city gate Context triple: [Jüterbog, hasLandmark, Dammtor city gate]
-
A.
Millerntor city gate
The Millerntor city gate was a historic gate in Hamburg’s former city fortifications, giving its name to the surrounding area and later to the Millerntor-Stadion.
-
B.
Rieder Tor
Rieder Tor is a historic city gate in Donauwörth, Germany, and one of the town’s best-known architectural landmarks.
-
C.
Siegestor
The Siegestor is a 19th-century triumphal arch in Munich, Germany, dedicated to Bavarian military glory and located between the districts of Maxvorstadt and Schwabing.
-
D.
Enderttor city gate
Enderttor city gate is a historic medieval gate and former fortification in the town of Cochem, Germany.
-
E.
Hampoort city gate
Hampoort city gate is a historic town gate in Grave, Netherlands, notable as a remnant of the city’s former fortifications.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Dammtor city gate Triple: [Jüterbog, hasLandmark, Dammtor city gate]
Generated description
The Dammtor city gate is a historic medieval gate in Jüterbog, Germany, that once formed part of the town’s defensive fortifications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Dammtor city gate Target entity description: The Dammtor city gate is a historic medieval gate in Jüterbog, Germany, that once formed part of the town’s defensive fortifications.
-
A.
Millerntor city gate
The Millerntor city gate was a historic gate in Hamburg’s former city fortifications, giving its name to the surrounding area and later to the Millerntor-Stadion.
-
B.
Rieder Tor
Rieder Tor is a historic city gate in Donauwörth, Germany, and one of the town’s best-known architectural landmarks.
-
C.
Siegestor
The Siegestor is a 19th-century triumphal arch in Munich, Germany, dedicated to Bavarian military glory and located between the districts of Maxvorstadt and Schwabing.
-
D.
Enderttor city gate
Enderttor city gate is a historic medieval gate and former fortification in the town of Cochem, Germany.
-
E.
Hampoort city gate
Hampoort city gate is a historic town gate in Grave, Netherlands, notable as a remnant of the city’s former fortifications.
- F. None of above. chosen
Provenance (5 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66763ee908190af64af31b4ca2377 |
completed | April 20, 2026, 5:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a082de0208c81909b9e87332d159fe0 |
completed | May 16, 2026, 8:42 a.m. |
| NEDg | Description generation | batch_6a082f3ec3bc8190b9a499671247c02f |
completed | May 16, 2026, 8:47 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0830ccfdd881909cbf1c3fd2342821 |
completed | May 16, 2026, 8:54 a.m. |
Created at: April 11, 2026, 11:32 p.m.