Triple
T21999528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Army 8 Mountain Division |
E543287
|
entity |
| Predicate | warfareDomain |
P17742
|
FINISHED |
| Object | land warfare |
—
|
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: land warfare | Statement: [Indian Army 8 Mountain Division, warfareDomain, land warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warfareDomain Context triple: [Indian Army 8 Mountain Division, warfareDomain, land warfare]
-
A.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
B.
militaryDomain
chosen
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
-
C.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
D.
functionInWarfare
Indicates the role, purpose, or operational function that something serves within a military or warfare context.
-
E.
levelOfWar
Indicates the specific intensity or scale of military conflict at which an operation, action, or relationship is occurring (e.g., tactical, operational, strategic).
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12768c0088190b0c8d5cd9b7bf710 |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:19 p.m.