Triple
T31409817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idealist Hearths |
E801228
|
entity |
| Predicate | hasParamilitaryAspect |
P4659
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Idealist Hearths, hasParamilitaryAspect, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParamilitaryAspect Context triple: [Idealist Hearths, hasParamilitaryAspect, true]
-
A.
paramilitaryRole
Indicates that an entity serves in, is associated with, or performs functions for a paramilitary organization or unit.
-
B.
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.
-
C.
isMilitarized
Indicates that an entity is organized, equipped, or structured according to military principles, forces, or purposes.
-
D.
wasMilitarized
Indicates that an entity underwent a process of being organized, equipped, or adapted for military use or purposes.
-
E.
paramilitaryWing
Indicates that one entity functions as the paramilitary or armed wing associated with another entity, typically an organization or movement.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: April 30, 2026, 8:37 p.m.