Triple
T6152049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Party (UK) |
E137225
|
entity |
| Predicate | usedParamilitaryElements |
P4659
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [New Party (UK), usedParamilitaryElements, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedParamilitaryElements Context triple: [New Party (UK), usedParamilitaryElements, yes]
-
A.
paramilitary
chosen
Indicates that an entity is associated with an organized, armed group that operates similarly to a military force but is not part of the official state military.
-
B.
militaryForceUsed
Indicates that one entity employs or applies military power or armed force against, within, or in relation to another entity or situation.
-
C.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
D.
postMilitaryUse
Indicates that an entity is used or repurposed after its original military function or service has ended.
-
E.
militaryTacticsUsed
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
- 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_69c008a45d008190832a9e19f5d63406 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cfcb5cc8190b998e92211810442 |
completed | March 22, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.