Triple
T14864620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna Gate |
E349584
|
entity |
| Predicate | hasNameInGerman |
P22792
|
FINISHED |
| Object |
Wiener Tor
Wiener Tor is the German name for the historic Vienna Gate, a former city gate associated with access to Vienna.
|
E1123484
|
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: Wiener Tor | Statement: [Vienna Gate, hasNameInGerman, Wiener Tor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wiener Tor Context triple: [Vienna Gate, hasNameInGerman, Wiener Tor]
-
A.
Hallesches Tor
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.
Bécsi kapu
Bécsi kapu is a historic city gate and square in Budapest’s Castle District, serving as one of the main entrances to the Buda Castle area.
-
E.
Osthofentor
Osthofentor is a historic city gate in Soest, Germany, notable as one of the best-preserved remnants of the town’s medieval 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: Wiener Tor Triple: [Vienna Gate, hasNameInGerman, Wiener Tor]
Generated description
Wiener Tor is the German name for the historic Vienna Gate, a former city gate associated with access to Vienna.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Wiener Tor Target entity description: Wiener Tor is the German name for the historic Vienna Gate, a former city gate associated with access to Vienna.
-
A.
Hallesches Tor
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.
Bécsi kapu
chosen
Bécsi kapu is a historic city gate and square in Budapest’s Castle District, serving as one of the main entrances to the Buda Castle area.
-
E.
Osthofentor
Osthofentor is a historic city gate in Soest, Germany, notable as one of the best-preserved remnants of the town’s medieval fortifications.
- F. None of above.
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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded574d0ec8190a6afed672ba6c2f9 |
completed | April 15, 2026, 12:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe6b4f224c8190bb2e06203c9b3a94 |
completed | May 8, 2026, 11:01 p.m. |
| NEDg | Description generation | batch_69fe6c68c46881909e7c748c0dff73d5 |
completed | May 8, 2026, 11:06 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69fe6d1eea60819087ca2ebc7d0a8994 |
completed | May 8, 2026, 11:09 p.m. |
Created at: April 10, 2026, 1:54 a.m.