Triple
T13137837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schierke |
E312128
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Brocken |
E79319
|
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: Brocken | Statement: [Schierke, locatedNear, Brocken]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brocken Context triple: [Schierke, locatedNear, Brocken]
-
A.
Brocken
chosen
Brocken is a prominent mountain in central Germany’s Harz range, known for its harsh climate, folklore, and role in literature and cultural history.
-
B.
Bärenkopf
Bärenkopf is a mountain peak in the Austrian Alps that forms part of the Glockner Group.
-
C.
Teufelstättkopf
Teufelstättkopf is a mountain peak in the Bavarian Ammergau Alps, popular with hikers for its scenic views and relatively accessible trails.
-
D.
Kofel
Kofel is a distinctive, steep limestone peak overlooking the town of Oberammergau in the Ammergau Alps of Bavaria, Germany, popular with hikers and climbers.
-
E.
Berghaupten
Berghaupten is a small municipality in the Ortenau district of Baden-Württemberg in southwestern Germany, known for its scenic location in the Black Forest region.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b6a4348190b9922ed255759078 |
completed | April 10, 2026, 11:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f71f1191e48190a504299a1f9afb2c |
completed | May 3, 2026, 10:10 a.m. |
Created at: April 9, 2026, 9:09 p.m.