Triple
T11551734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nolin River Lake project |
E273910
|
entity |
| Predicate | waterbodyTypeControlled |
P1011
|
FINISHED |
| Object | reservoir |
—
|
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: reservoir | Statement: [Nolin River Lake project, waterbodyTypeControlled, reservoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterbodyTypeControlled Context triple: [Nolin River Lake project, waterbodyTypeControlled, reservoir]
-
A.
watercourseControlled
Indicates that one entity exercises control, regulation, or management over a watercourse (such as a river, stream, or canal).
-
B.
waterbodyType
chosen
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
C.
overseesBodyOfWater
Indicates that one entity has administrative, regulatory, or managerial authority over a particular body of water.
-
D.
waterbodyUsedFor
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
-
E.
waterbodyID
Indicates a unique identifier that links an entity to a specific body of water.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a83f1e88190aabf11a4c8a6c9e5 |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d8087e57b48190a4c253dc0210f9d4 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.