Triple
T31740699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shillong Lok Sabha constituency |
E810131
|
entity |
| Predicate | coversDistrict |
P22582
|
FINISHED |
| Object | East Khasi Hills 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: East Khasi Hills district | Statement: [Shillong Lok Sabha constituency, coversDistrict, East Khasi Hills district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversDistrict Context triple: [Shillong Lok Sabha constituency, coversDistrict, East Khasi Hills district]
-
A.
includesDistrict
chosen
Indicates that one administrative or geographic entity contains or encompasses a specific district within its boundaries.
-
B.
appliesToDistrict
Indicates that something (such as a rule, policy, or condition) is relevant or applicable to a specific district.
-
C.
occursInDistrict
Indicates that an event or activity takes place within the boundaries of a specific district.
-
D.
coversCity
Indicates that one entity extends over, includes, or geographically encompasses the area of a specified city.
-
E.
servedDistrict
Indicates that an entity has provided official service or representation to a particular district.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 30, 2026, 11:24 p.m.