Triple
T4286716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taunus |
E97286
|
entity |
| Predicate | hasPeak |
P8205
|
FINISHED |
| Object | Altkönig |
E213065
|
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: Altkönig | Statement: [Taunus, hasPeak, Altkönig]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Altkönig Context triple: [Taunus, hasPeak, Altkönig]
-
A.
Altkönig
chosen
Altkönig is a prominent mountain peak in Germany’s Taunus range, known for its scenic hiking trails and remains of ancient Celtic fortifications.
-
B.
Kronsberg
Kronsberg is a location in Germany known, among other things, as the place where former Nazi youth leader Baldur von Schirach died.
-
C.
Königsbau
Königsbau is a prominent wing of the Munich Residenz, built in the 19th century in a neo-classical style as royal apartments for the Bavarian kings.
-
D.
Roter Turm
Roter Turm is a historic medieval tower and prominent architectural landmark in the city center of Chemnitz, Germany.
-
E.
Roter Turm
Roter Turm is a historic clock and bell tower in Halle (Saale), Germany, and one of the city’s most recognizable architectural landmarks.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3505d23d88190a638f2cc2acee9ee |
completed | March 12, 2026, 11:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5b7c8c1ac819086ded38c1abe9b63 |
completed | March 14, 2026, 7:32 p.m. |
Created at: March 12, 2026, 11:08 p.m.