Triple
T26669170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceded Districts |
E672274
|
entity |
| Predicate | majorRiverSystemNearby |
P36808
|
FINISHED |
| Object | Tungabhadra 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: Tungabhadra River | Statement: [Ceded Districts, majorRiverSystemNearby, Tungabhadra River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRiverSystemNearby Context triple: [Ceded Districts, majorRiverSystemNearby, Tungabhadra River]
-
A.
nearbyRiverProject
Indicates that there is a project located close to or associated with a nearby river.
-
B.
closelyAssociatedRiver
Indicates a river that is geographically or functionally closely connected to the subject, such as flowing nearby, through, or otherwise strongly linked to it.
-
C.
nearbyWatercourse
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
-
D.
hasMajorRiverSystem
chosen
Indicates that an entity possesses or is traversed by a primary, large-scale river network that significantly characterizes its hydrology or geography.
-
E.
useRiverSystems
Indicates that an entity utilizes or manages river systems for a particular purpose or function.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 27, 2026, 3:11 a.m.