Triple
T27101844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonowal Kachari |
E686461
|
entity |
| Predicate | governmentReservationCategory |
P194237
|
FINISHED |
| Object | ST (Scheduled Tribe) |
—
|
LITERAL 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: ST (Scheduled Tribe) | Statement: [Sonowal Kachari, governmentReservationCategory, ST (Scheduled Tribe)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentReservationCategory Context triple: [Sonowal Kachari, governmentReservationCategory, ST (Scheduled Tribe)]
-
A.
governmentCategory
Indicates the type or classification of a government associated with an entity.
-
B.
governmentOwned
Indicates that an entity is owned or controlled by a government or public authority.
-
C.
militaryGovernment
Indicates a relationship where a government is controlled or dominated by military authorities rather than civilian leadership.
-
D.
governmentClient
Indicates a relationship where one entity serves as a client or customer of a government or governmental body.
-
E.
recognizedGovernment
Indicates that one entity formally acknowledges another entity as the legitimate governing authority of a state or territory.
- F. None of above. chosen
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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
| PDg | Predicate description generation | batch_69fd68ab21a0819096bfc4a8c14851ad |
completed | May 8, 2026, 4:38 a.m. |
Created at: April 27, 2026, 8:48 a.m.