Triple
T18107773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hinterer Bratschenkopf |
E433388
|
entity |
| Predicate | hasNearbyPeak |
P7612
|
FINISHED |
| Object | Vorderer Bratschenkopf |
—
|
NE NERFINISHED |
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: Vorderer Bratschenkopf | Statement: [Hinterer Bratschenkopf, hasNearbyPeak, Vorderer Bratschenkopf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vorderer Bratschenkopf Context triple: [Hinterer Bratschenkopf, hasNearbyPeak, Vorderer Bratschenkopf]
-
A.
Vorderer Bratschenkopf
chosen
Vorderer Bratschenkopf is a mountain peak in the Austrian Alps, located within the Glockner Group of the High Tauern range.
-
B.
Hinterer Bratschenkopf
Hinterer Bratschenkopf is a high alpine peak in the Austrian Central Alps, located within the Glockner Group of the Hohe Tauern range.
-
C.
Grünbein
Grünbein is a German surname most notably borne by the contemporary poet and essayist Durs Grünbein.
-
D.
Fuscherkarkopf
Fuscherkarkopf is a prominent alpine peak in the Austrian Alps, known for its high elevation and location within the Glockner Group of the Hohe Tauern range.
-
E.
Schievelbein
Schievelbein is a historic town in Pomerania, now known as Świdwin in northwestern Poland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddbb3d408190b5fc7870bc6512f4 |
completed | April 19, 2026, 1:50 p.m. |
Created at: April 10, 2026, 10:28 a.m.