Triple
T10852568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vamma power station |
E256183
|
entity |
| Predicate | hasRunOfRiverDesign |
P50031
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Vamma power station, hasRunOfRiverDesign, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunOfRiverDesign Context triple: [Vamma power station, hasRunOfRiverDesign, true]
-
A.
runOfTheRiver
chosen
Indicates a relationship where a hydroelectric facility operates using the natural flow and elevation drop of a river without significant water storage or regulation by a large reservoir.
-
B.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
operatesOnRiver
Indicates that an entity conducts its operations or activities on, along, or directly involving a river.
-
D.
hasFictionalRiver
Indicates that an entity includes, features, or is associated with a river that is fictional rather than real.
-
E.
isOnlyNavigableRiverOf
Indicates that one river is the sole river that can be navigated within a specified area or context.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75134299481909459fd87917261a7 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.