Triple
T30901673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajahmundry Lok Sabha constituency |
E787185
|
entity |
| Predicate | borderingConstituencyRegion |
P197704
|
FINISHED |
| Object | Godavari River basin |
—
|
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: Godavari River basin | Statement: [Rajahmundry Lok Sabha constituency, borderingConstituencyRegion, Godavari River basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingConstituencyRegion Context triple: [Rajahmundry Lok Sabha constituency, borderingConstituencyRegion, Godavari River basin]
-
A.
borderingConstituency
Indicates that one political constituency shares a common boundary with another constituency.
-
B.
borderingConstituencyState
Indicates that a constituency shares a common boundary with a particular state.
-
C.
isBorderConstituency
Indicates that a constituency lies along or adjacent to a national or regional border.
-
D.
borderingCensusDivision
Indicates that one census division shares a common boundary with another census division.
-
E.
borderingLocalGovernmentArea
Indicates that one local government area shares a common boundary with another local government area.
- F. None of above. chosen
Provenance (4 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fea2cfcd648190a15e5b90889095b1 |
completed | May 9, 2026, 2:58 a.m. |
Created at: April 29, 2026, 8:50 p.m.