Triple
T26602180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dimasa Kachari |
E667663
|
entity |
| Predicate | autonomousCouncilRegion |
P11102
|
FINISHED |
| Object | North Cachar Hills Autonomous Council (now NCHAC) |
—
|
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: North Cachar Hills Autonomous Council (now NCHAC) | Statement: [Dimasa Kachari, autonomousCouncilRegion, North Cachar Hills Autonomous Council (now NCHAC)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autonomousCouncilRegion Context triple: [Dimasa Kachari, autonomousCouncilRegion, North Cachar Hills Autonomous Council (now NCHAC)]
-
A.
isCouncilAreaOf
chosen
Indicates that one entity is the officially designated council (local government) area that administers or governs the other entity.
-
B.
governmentDistrict
Indicates that a government entity has jurisdiction over or is administratively associated with a specific district.
-
C.
hasCouncilAreaStatusFrom
Indicates that an entity holds council area status starting from a specified point in time.
-
D.
hasCouncilAreaName
Indicates that an entity is associated with a council area identified by a specific name.
-
E.
hasCouncilAreaCode
Indicates that an entity is associated with a specific council area identified by a particular code.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61570d4e08190bbe6f89efc3b9b54 |
completed | May 2, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 2:13 a.m.