Triple
T30828087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nag River Rejuvenation Project |
E785131
|
entity |
| Predicate | targetsRiver |
P180780
|
FINISHED |
| Object | Nag 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: Nag River | Statement: [Nag River Rejuvenation Project, targetsRiver, Nag River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsRiver Context triple: [Nag River Rejuvenation Project, targetsRiver, Nag River]
-
A.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
B.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
associatedRiverBasin
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
-
D.
betweenRiver
Indicates a spatial relationship where something is located in the area separating two rivers or lies in the intermediate region defined by them.
-
E.
linkedToRiver
chosen
Indicates a relationship where something is physically or functionally connected to, associated with, or dependent on 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 29, 2026, 8:44 p.m.