Triple
T8639471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITBP |
E204605
|
entity |
| Predicate | typeOfBorderGuardingForce |
P81735
|
FINISHED |
| Object | Indo-China border guarding force |
—
|
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: Indo-China border guarding force | Statement: [ITBP, typeOfBorderGuardingForce, Indo-China border guarding force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBorderGuardingForce Context triple: [ITBP, typeOfBorderGuardingForce, Indo-China border guarding force]
-
A.
typeOfGovernmentForces
Indicates the specific kind or classification of government-controlled military or security forces involved in a situation or context.
-
B.
typeOfCadetForce
Indicates the specific category or kind of cadet force to which an entity belongs.
-
C.
numberOfBorderGuards
Indicates the quantity of border guards associated with a given location, event, or entity.
-
D.
hasBorderGuardingMandateWith
Indicates that one entity has an official responsibility or mandate to guard, monitor, or secure a border in cooperation or association with another entity.
-
E.
typeOfFrontierUnit
chosen
Indicates that one unit is classified as a specific type or category of frontier unit in relation to another.
- 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_69ca834ca1c88190a11ffb0200342fac |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc47944d1c819081f448f14d04bf9d |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:28 p.m.