Triple
T5443532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sideways |
E122192
|
entity |
| Predicate | combatPreference |
P50132
|
FINISHED |
| Object | indirect attacks |
—
|
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: indirect attacks | Statement: [Sideways, combatPreference, indirect attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatPreference Context triple: [Sideways, combatPreference, indirect attacks]
-
A.
combatArm
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
-
B.
usedWarfareType
Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
-
C.
tacticalStyle
chosen
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
-
D.
combatOrNonCombat
Indicates whether an entity is involved in combat activities or is in a non-combat role or situation.
-
E.
builtForConflict
Indicates that something is specifically designed or intended to function effectively in situations of conflict or confrontation.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd922f66bc8190b7d47fd68d2fcf2e |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd919aeb048190b786f814177d6cd9 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.