Triple
T22508746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goindwal |
E556459
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Beas 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: Beas River | Statement: [Goindwal, locatedOn, Beas River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beas River Context triple: [Goindwal, locatedOn, Beas River]
-
A.
Beas River
chosen
The Beas River is a major river in northern India that flows through the state of Punjab, playing a vital role in its agriculture and ecology.
-
B.
Panj River
The Panj River is a significant Central Asian waterway that forms much of the border between Tajikistan and Afghanistan and serves as a principal headstream of the Amu Darya.
-
C.
Bhera River
The Bhera River is a significant tributary watercourse that feeds into eastern India’s Damodar River system.
-
D.
Panjnad River
The Panjnad River is a major waterway in Pakistan formed by the confluence of five rivers of the Punjab region, ultimately flowing into the Indus River.
-
E.
Khasa River
The Khasa River is a seasonal river in northern Iraq that flows through the city of Kirkuk and serves as one of its main waterways.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5ebe5881908a22d519128415f2 |
completed | April 29, 2026, 1:22 a.m. |
Created at: April 16, 2026, 8:50 p.m.