Triple
T8162186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krka River |
E190600
|
entity |
| Predicate | nearbyTown |
P3883
|
FINISHED |
| Object | Žužemberk |
E717188
|
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: Žužemberk | Statement: [Krka River, nearbyTown, Žužemberk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Žužemberk Context triple: [Krka River, nearbyTown, Žužemberk]
-
A.
Žužemberk
chosen
Žužemberk is a small historic town in southeastern Slovenia, known for its medieval castle and picturesque setting along the Krka River.
-
B.
Blansko
Blansko is a small industrial town in the South Moravian Region of the Czech Republic, known as a gateway to the Moravian Karst cave system.
-
C.
Husinec
Husinec is a small Czech town best known as the birthplace of the religious reformer Jan Hus.
-
D.
Osek
Osek is a town in the Czech Republic historically associated with the family origins of writer Franz Kafka’s father, Hermann Kafka.
-
E.
Beránek
Beránek is a Czech surname and word meaning "little lamb," commonly used as a family name in Czech-speaking regions.
- 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_69ca82c0ef14819083713f4473dd847c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4556b45c819089eb15ad027b036a |
completed | March 31, 2026, 3:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cced4e6efc8190a74aea4ab213298b |
completed | April 1, 2026, 10:02 a.m. |
Created at: March 30, 2026, 5:38 p.m.