Triple
T25656401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barak Valley |
E643248
|
entity |
| Predicate | comprisesDistrict |
P22582
|
FINISHED |
| Object | Hailakandi 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: Hailakandi district | Statement: [Barak Valley, comprisesDistrict, Hailakandi district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comprisesDistrict Context triple: [Barak Valley, comprisesDistrict, Hailakandi district]
-
A.
includesDistrict
chosen
Indicates that one administrative or geographic entity contains or encompasses a specific district within its boundaries.
-
B.
containsDistrictMunicipality
Indicates that an administrative region includes one or more district municipalities within its boundaries.
-
C.
geographicallySeparatedDistrictOf
Indicates that one district is a non-contiguous, physically separate part of another district or administrative area.
-
D.
hasCityDistrictAlong
Indicates that a city district is located along or adjacent to a specified linear feature, such as a road, river, or coastline.
-
E.
inCityDistrict
Indicates that one entity is located within the boundaries of a specific city 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 6:33 p.m.