Triple
T32745266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | सशस्त्र सीमा बल |
E837337
|
entity |
| Predicate | मुख्य कार्य |
P2166
|
FINISHED |
| Object | भारत-नेपाल सीमा की सुरक्षा |
—
|
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: भारत-नेपाल सीमा की सुरक्षा | Statement: [सशस्त्र सीमा बल, मुख्य कार्य, भारत-नेपाल सीमा की सुरक्षा]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: मुख्य कार्य Context triple: [सशस्त्र सीमा बल, मुख्य कार्य, भारत-नेपाल सीमा की सुरक्षा]
-
A.
primaryTask
chosen
Indicates that an entity has a main or most important task, role, or function it is responsible for above all others.
-
B.
primaryWork
Indicates that one work is the main or most significant work associated with a given entity, as opposed to other secondary or related works.
-
C.
mainlyPerformed
Indicates that an action or activity is carried out primarily or predominantly by a particular entity compared to others.
-
D.
الاختصاص الرئيسي
Indicates that one entity is the primary field of specialization or main area of focus for another entity.
-
E.
majorActivity
Indicates that the related entity performs, participates in, or is primarily associated with a main or most significant activity.
- 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.