Triple
T8037787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tapi River |
E187153
|
entity |
| Predicate | tributary |
P415
|
FINISHED |
| Object | Gomai River |
E726214
|
NE FINISHED |
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: Gomai River | Statement: [Tapi River, tributary, Gomai River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gomai River Context triple: [Tapi River, tributary, Gomai River]
-
A.
Gomai River
chosen
The Gomai River is a smaller river in western India that feeds into the larger Tapti River system.
-
B.
Saho River
The Saho River is a Japanese river in the Kansai region that forms part of the Yamato River system.
-
C.
Sonai River
The Sonai River is a tributary waterway in northeastern India that feeds into the larger Barak River system.
-
D.
Aruwimi River
The Aruwimi River is a significant river in the Democratic Republic of the Congo, known for flowing through dense equatorial rainforest and contributing substantially to the Congo River basin.
-
E.
Ngashih River
Ngashih River is a tributary watercourse in northeastern India that feeds into the larger Tlawng River system.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f19a6b4819085e2887fb0c54d08 |
completed | March 31, 2026, 3:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6f67c3a0881909f24d85d74e4c061 |
completed | April 9, 2026, 12:44 a.m. |
Created at: March 30, 2026, 5:23 p.m.