Triple
T37860110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bihar–Uttar Pradesh border |
E944302
|
entity |
| Predicate | adjacentDistrictInUttarPradesh |
P194050
|
FINISHED |
| Object | Ballia 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: Ballia district | Statement: [Bihar–Uttar Pradesh border, adjacentDistrictInUttarPradesh, Ballia district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentDistrictInUttarPradesh Context triple: [Bihar–Uttar Pradesh border, adjacentDistrictInUttarPradesh, Ballia district]
-
A.
governmentDistrict
Indicates that a government entity has jurisdiction over or is administratively associated with a specific district.
-
B.
adjacentProvince
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
C.
locatedNearGovernmentDistrict
Indicates that one entity is situated close to or in the immediate vicinity of a government district.
-
D.
adjacentCityOrTown
Indicates that one city or town is directly next to or bordering another city or town geographically.
-
E.
assemblyConstituencyNumberInUttarPradesh
Indicates the specific numerical identifier assigned to an assembly constituency within the state of Uttar Pradesh.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_69fd5d47da488190a4f2dbd44a0a83b2 |
completed | May 8, 2026, 3:49 a.m. |
Created at: May 3, 2026, 4:19 p.m.