Triple
T27843826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishing community |
E703759
|
entity |
| Predicate | autonomousCouncilState |
P28237
|
FINISHED |
| Object | Assam |
—
|
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: Assam | Statement: [Mishing community, autonomousCouncilState, Assam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autonomousCouncilState Context triple: [Mishing community, autonomousCouncilState, Assam]
-
A.
isCouncilAreaOf
Indicates that one entity is the officially designated council (local government) area that administers or governs the other entity.
-
B.
hasCouncilAreaStatusFrom
Indicates that an entity holds council area status starting from a specified point in time.
-
C.
hasCouncilAreaStatus
chosen
Indicates that an entity holds the official designation or status of being a council area within an administrative or governmental structure.
-
D.
hasCouncilAreaName
Indicates that an entity is associated with a council area identified by a specific name.
-
E.
unionTerritoryWithoutLegislature
Indicates that a union territory exists under central administration without having its own legislative assembly or lawmaking body.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f638d838c481909fbe470bb85c30b1 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:05 p.m.