Triple
T37860105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bihar–Uttar Pradesh border |
E944302
|
entity |
| Predicate | adjacentDistrictInBihar |
P17964
|
FINISHED |
| Object | Buxar district |
—
|
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: Buxar district | Statement: [Bihar–Uttar Pradesh border, adjacentDistrictInBihar, Buxar district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentDistrictInBihar Context triple: [Bihar–Uttar Pradesh border, adjacentDistrictInBihar, Buxar district]
-
A.
adjacentProvince
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
B.
governmentDistrict
Indicates that a government entity has jurisdiction over or is administratively associated with a specific district.
-
C.
neighboringRegion
chosen
Indicates that two regions share a common boundary or are directly adjacent to each other geographically.
-
D.
populationRankInBihar
Indicates the relative position of an entity in an ordered list based on its population size within the state of Bihar.
-
E.
borderingBhutaneseDistricts
Indicates that the specified Bhutanese districts share a common boundary with each other.
- 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_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 3, 2026, 4:19 p.m.