Triple
T18932135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghaggar River |
E463138
|
entity |
| Predicate | flowsNear |
P350
|
FINISHED |
| Object | Hanumangarh |
—
|
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: Hanumangarh | Statement: [Ghaggar River, flowsNear, Hanumangarh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanumangarh Context triple: [Ghaggar River, flowsNear, Hanumangarh]
-
A.
Hanumangarh
chosen
Hanumangarh is a town in the northern Indian state of Rajasthan, known for serving as an administrative and commercial center near the Ghaggar River and the Punjab border.
-
B.
Deogarh
Deogarh was a historic kingdom ruled by the Gonds, an indigenous community in central India.
-
C.
Deogarh
Deogarh is a prominent city in the Kosal region of India, known for its historical and cultural significance.
-
D.
Sujangarh
Sujangarh is a town in the Indian state of Rajasthan known for its local markets, temples, and role as a regional commercial center.
-
E.
Titlagarh
Titlagarh is a town and important railway junction in the Balangir district of Odisha, India, serving as a key transit point in the region.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9c0b84881909ad6da9522203df8 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 10, 2026, 11:59 a.m.