Triple
T11771389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brezno |
E279905
|
entity |
| Predicate | hasNearbyPeak |
P7612
|
FINISHED |
| Object | Ďumbier |
E300713
|
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: Ďumbier | Statement: [Brezno, hasNearbyPeak, Ďumbier]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ďumbier Context triple: [Brezno, hasNearbyPeak, Ďumbier]
-
A.
Ďumbier
chosen
Ďumbier is a prominent mountain peak in central Slovakia known for its alpine scenery, hiking trails, and panoramic views over the surrounding Carpathian ranges.
-
B.
Nabo
Nabo is a diminutive form of the given name Nabil, often used as a familiar or affectionate nickname.
-
C.
Barbula
Barbula was a cognomen of the ancient Roman gens Aemilia, borne by several members of this prominent patrician family.
-
D.
Bramsche
Bramsche is a town in Lower Saxony, Germany, known for its location near Osnabrück and its historical textile industry.
-
E.
Biberwier
Biberwier is a small alpine village and municipality in the Tyrolean Zugspitz Arena of western Austria, known for its mountain scenery and outdoor recreation.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a55c9f988190b203b66a28c767ae |
completed | April 10, 2026, 7:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f09086c4ec81908bc8b707a49c3ac2 |
completed | April 28, 2026, 10:48 a.m. |
Created at: April 8, 2026, 9:41 p.m.