Triple
T30531407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Šance Reservoir |
E777013
|
entity |
| Predicate | hasDamOn |
P8736
|
FINISHED |
| Object | Ostravice 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: Ostravice River | Statement: [Šance Reservoir, hasDamOn, Ostravice River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDamOn Context triple: [Šance Reservoir, hasDamOn, Ostravice River]
-
A.
hasDam
chosen
Indicates that a watercourse, reservoir, or similar feature is impounded or controlled by a specific dam.
-
B.
hasDamCount
Indicates the number of dams associated with or present on a given entity (such as a river, region, or site).
-
C.
hasDamFunction
Indicates that something serves the role or performs the function of a dam, such as impounding or regulating the flow of water.
-
D.
hasTypeOfDamage
Indicates that an entity experiences or exhibits a specific kind or category of damage.
-
E.
damagedIn
Indicates that an entity has suffered harm, impairment, or destruction as a result of a specified event, process, or condition.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:18 p.m.