Triple
T32745278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | सशस्त्र सीमा बल |
E837337
|
entity |
| Predicate | नियंत्रण |
P4700
|
FINISHED |
| Object | केंद्रीय सरकार |
—
|
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: केंद्रीय सरकार | Statement: [सशस्त्र सीमा बल, नियंत्रण, केंद्रीय सरकार]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: नियंत्रण Context triple: [सशस्त्र सीमा बल, नियंत्रण, केंद्रीय सरकार]
-
A.
controlled
chosen
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
-
B.
centralizesControlOf
Indicates that one entity consolidates and concentrates decision-making authority or governance power over another entity or set of entities.
-
C.
aimsToControl
Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
-
D.
controlledIn
Indicates that one entity exercised control, authority, or governance over another entity within a specific context or domain.
-
E.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:12 a.m.