Triple
T32745293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | सशस्त्र सीमा बल |
E837337
|
entity |
| Predicate | संबंधित श्रेणी |
P127424
|
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.
relatedClassification
chosen
Indicates a relationship where one classification is associated with, linked to, or otherwise contextually connected to another classification.
-
B.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
D.
seriesRelation
Indicates a relationship where one entity is part of, follows from, or is otherwise connected to another within an ordered series or sequence.
-
E.
संबंधित वंश
Indicates a relationship where one entity belongs to, descends from, or is associated with a particular lineage or ancestry.
- 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.