Triple
T31951665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Austria and South Moravia |
E815795
|
entity |
| Predicate | hasCrossBorderRiver |
P93095
|
FINISHED |
| Object | Thaya River |
—
|
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: Thaya River | Statement: [Lower Austria and South Moravia, hasCrossBorderRiver, Thaya River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrossBorderRiver Context triple: [Lower Austria and South Moravia, hasCrossBorderRiver, Thaya River]
-
A.
bordersAcrossRiver
Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
-
B.
borderedByCountryAcrossRiver
Indicates that one country shares a border with another country, with the boundary specifically formed or separated by a river.
-
C.
isOnBorderRiver
Indicates that something is located along or directly adjacent to a river that forms a border between areas.
-
D.
transboundaryRiverOf
chosen
Indicates that a river crosses or forms the boundary between two or more political or administrative regions.
-
E.
hasRiverCounterpart
Indicates that one entity has a corresponding or analogous counterpart in the context of a river.
- F. None of above.
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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 1, 2026, 12:07 a.m.