Triple
T8090246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pardubice Region |
E188838
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | Orlice |
E129687
|
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: Orlice | Statement: [Pardubice Region, hasRiver, Orlice]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orlice Context triple: [Pardubice Region, hasRiver, Orlice]
-
A.
Orlice
chosen
Orlice is a river in the Czech Republic that flows through the city of Hradec Králové and is a tributary of the Labe (Elbe) River.
-
B.
Orlice River
The Orlice River is a significant river in the Czech Republic that flows through eastern Bohemia and joins the Elbe near the city of Hradec Králové.
-
C.
Pirna
Pirna is a historic town in eastern Germany situated on the River Elbe, known as a gateway to the Saxon Switzerland National Park.
-
D.
Weschnitz
Weschnitz is a river in southwestern Germany that flows from the Odenwald hills through Hesse and Baden-Württemberg before joining the Rhine.
-
E.
Würschnitz
Würschnitz is a small river in Saxony, Germany, that serves as one of the tributaries feeding into the Chemnitz River.
- 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_69ca82b7b3e88190b9041ab0ef28b3cb |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb421e30e88190b9699b338b69b81c |
completed | March 31, 2026, 3:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc93ff6a108190ac60218ec2716c60 |
completed | April 1, 2026, 3:41 a.m. |
Created at: March 30, 2026, 5:29 p.m.