Triple
T30215035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundararaja Perumal |
E768179
|
entity |
| Predicate | isAssociatedWithRiver |
P165
|
FINISHED |
| Object | Vaigai 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: Vaigai River | Statement: [Sundararaja Perumal, isAssociatedWithRiver, Vaigai River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssociatedWithRiver Context triple: [Sundararaja Perumal, isAssociatedWithRiver, Vaigai River]
-
A.
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.
-
B.
hasRiver
chosen
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.
mainRiverAssociated
Indicates that one entity is associated with, or primarily linked to, a particular main river.
-
E.
hasRiverCounterpart
Indicates that one entity has a corresponding or analogous counterpart in the context of 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff517908190ad290edafd6c6f5f |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:33 p.m.