Triple
T8739065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRPF |
E207456
|
entity |
| Predicate | specializedUnitRole |
P9463
|
FINISHED |
| Object | jungle warfare and anti-Naxal operations |
—
|
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: jungle warfare and anti-Naxal operations | Statement: [CRPF, specializedUnitRole, jungle warfare and anti-Naxal operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specializedUnitRole Context triple: [CRPF, specializedUnitRole, jungle warfare and anti-Naxal operations]
-
A.
unitSpecialization
Indicates that one unit is a specialized or more specific version of another unit within a hierarchical or categorical relationship.
-
B.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
C.
specialRole
Indicates that an entity holds a distinctive or exceptional function, status, or responsibility in relation to another entity or context.
-
D.
hasSpecialUnit
Indicates that an entity possesses or is associated with a distinct, designated unit that has a special role, function, or status.
-
E.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
- 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_69ca835a03a081909d4d4cd01a18c9fb |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d470c8c81909ead395ef704c6ba |
completed | March 31, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69cc457322b481908712a9630a17b954 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:38 p.m.