Triple
T30418683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rożnów |
E773831
|
entity |
| Predicate | hasNearbyHydrotechnicalStructure |
P127358
|
FINISHED |
| Object | Rożnów Dam |
—
|
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: Rożnów Dam | Statement: [Rożnów, hasNearbyHydrotechnicalStructure, Rożnów Dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHydrotechnicalStructure Context triple: [Rożnów, hasNearbyHydrotechnicalStructure, Rożnów Dam]
-
A.
hasNearbyRiverStructure
chosen
Indicates that a river-related structure (such as a dam, bridge, or levee) is located close to the referenced entity.
-
B.
hasNearbyWaterInfrastructure
Indicates that a location or entity is situated close to water-related infrastructure such as pipes, treatment facilities, or distribution systems.
-
C.
hasHydroelectricInfrastructureNearby
Indicates that there is hydroelectric infrastructure located in close proximity to the referenced entity.
-
D.
nearbyMajorDam
Indicates that one entity is located close to a significant dam structure in its surrounding area.
-
E.
nearbyDownstreamDam
Indicates that one dam is located a short distance downstream from another along the same watercourse.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: April 29, 2026, 8:05 p.m.