Triple
T37860091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bihar–Uttar Pradesh border |
E944302
|
entity |
| Predicate | followsRiverInSections |
P3624
|
FINISHED |
| Object | Ganges 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: Ganges River | Statement: [Bihar–Uttar Pradesh border, followsRiverInSections, Ganges River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsRiverInSections Context triple: [Bihar–Uttar Pradesh border, followsRiverInSections, Ganges River]
-
A.
followsSectionOf
Indicates that one section directly comes after or succeeds another section in an ordered structure.
-
B.
followsSect
Indicates that one entity adheres to, practices, or is a member of a particular sect associated with another entity.
-
C.
waterwayFollowed
Indicates that one entity moves along or traces the course of a particular waterway (such as a river, canal, or stream).
-
D.
followsWatercourse
chosen
Indicates that one entity runs alongside or traces the path of a watercourse such as a river, stream, or canal.
-
E.
downstreamRiverSection
Indicates that one river section is located downstream from, and receives flow from, another river section.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.