Triple
T35392799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jahanabad Lok Sabha constituency |
E1022985
|
entity |
| Predicate | includesAreasOfDistrict |
P22582
|
FINISHED |
| Object | Gaya district |
E281283
|
NE FINISHED |
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: Gaya district | Statement: [Jahanabad Lok Sabha constituency, includesAreasOfDistrict, Gaya district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesAreasOfDistrict Context triple: [Jahanabad Lok Sabha constituency, includesAreasOfDistrict, Gaya district]
-
A.
includesDistrict
chosen
Indicates that one administrative or geographic entity contains or encompasses a specific district within its boundaries.
-
B.
includesAreaOf
Indicates that one entity encompasses or contains the spatial extent or area covered by another entity.
-
C.
electoralDistrictIncludes
Indicates that a given electoral district geographically contains or encompasses a specified area or location.
-
D.
appliesToDistrict
Indicates that something (such as a rule, policy, or condition) is relevant or applicable to a specific district.
-
E.
includesAreasOff
Indicates that something encompasses or covers areas that are turned off, inactive, or excluded from normal operation.
- F. None of above.
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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3836ac5f2081909499c8e0ac104372 |
completed | June 21, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.