Triple
T25657453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Srirangam Island |
E643273
|
entity |
| Predicate | separatesRiver |
P159480
|
FINISHED |
| Object | Kaveri 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: Kaveri River | Statement: [Srirangam Island, separatesRiver, Kaveri River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatesRiver Context triple: [Srirangam Island, separatesRiver, Kaveri River]
-
A.
riverSeparatingFrom
Indicates that one river branches off or diverges from another river, creating a separation between their flow paths.
-
B.
betweenRiver
Indicates a spatial relationship where something is located in the area separating two rivers or lies in the intermediate region defined by them.
-
C.
separatesRiverSystemsFlowingTo
Indicates that one entity acts as a dividing feature that causes river systems on either side to flow toward different drainage basins or destinations.
-
D.
riverSeparatingCity
Indicates that a river runs between and divides parts of a city or separates one city from another.
-
E.
bordersAcrossRiver
Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
- F. None of above. chosen
Provenance (4 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faece90c8190826cd3bd3614c10d |
completed | May 2, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 21, 2026, 6:35 p.m.