Triple
T16206138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tábor District |
E393331
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | Lužnice |
E1229143
|
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: Lužnice | Statement: [Tábor District, hasRiver, Lužnice]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lužnice Context triple: [Tábor District, hasRiver, Lužnice]
-
A.
Lužnice
chosen
Lužnice is a village and municipality in the South Bohemian Region of the Czech Republic, known for its location near the Lužnice River and its natural surroundings.
-
B.
Pohořelice
Pohořelice is a small town in the South Moravian Region of the Czech Republic, known for its agricultural surroundings and proximity to the city of Brno.
-
C.
Luž
Luž is the highest peak of the Lusatian Mountains, a prominent mountain on the Czech-German border known for its scenic views and hiking trails.
-
D.
Lubenice
Lubenice is a small, historic hilltop village on the Croatian island of Cres, known for its stone architecture, dramatic cliffs, and views over the Adriatic Sea.
-
E.
Lovosice
Lovosice is a town in the Czech Republic, historically notable as the site of the 1756 Battle of Lobositz during the Seven Years' War.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2270f047c819084645da27759a3d2 |
completed | April 17, 2026, 12:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00a5047a7c8190bac0ac9888547d16 |
completed | May 10, 2026, 3:32 p.m. |
Created at: April 10, 2026, 5:03 a.m.