Triple
T17764916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mönchsberg |
E443477
|
entity |
| Predicate | formsRidgeWith |
P91361
|
FINISHED |
| Object | Festungsberg |
—
|
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: Festungsberg | Statement: [Mönchsberg, formsRidgeWith, Festungsberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Festungsberg Context triple: [Mönchsberg, formsRidgeWith, Festungsberg]
-
A.
Festungsberg
chosen
Festungsberg is a prominent hill in Salzburg, Austria, best known as the site of the medieval Hohensalzburg Fortress overlooking the city.
-
B.
Aegidienberg
Aegidienberg is a district of the town of Bad Honnef in North Rhine-Westphalia, Germany, known for its scenic location in the Siebengebirge region.
-
C.
Witzmannsberg
Witzmannsberg is a small rural municipality in the Bavarian region of Lower Bavaria, Germany, known for its scenic countryside and traditional village character.
-
D.
Oberhalbstein
Oberhalbstein is a high Alpine valley and region in the canton of Graubünden, Switzerland, known for its Romansh-speaking communities and mountain landscapes.
-
E.
Schneidhain
Schneidhain is a district of the town Königstein im Taunus in the Hochtaunus region of Hesse, Germany.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fb2a3c81908887d1d36aee942d |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 10:11 a.m.