Triple
T14707270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faith Militant |
E345458
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | armed religious organization |
C35054
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: armed religious organization Context triple: [Faith Militant, instanceOf, armed religious organization]
-
A.
religiously inspired organization
A religiously inspired organization is a group whose mission, values, and activities are significantly shaped by specific religious beliefs, teachings, or traditions, even if it operates in secular domains.
-
B.
former religious organization
A former religious organization is a once-active group formally dedicated to shared religious beliefs and practices that has since disbanded, dissolved, or otherwise ceased to function as an organized entity.
-
C.
religious social group
A religious social group is a community of individuals who share and collectively practice a common set of spiritual beliefs, rituals, and moral values, often organized around a specific faith tradition or denomination.
-
D.
religious league
A religious league is an organized alliance of states, groups, or individuals united primarily by shared religious beliefs or interests to pursue common political, military, or social goals.
-
E.
organ of an international religious organization
An organ of an international religious organization is a formally established body or office within the organization that carries out specific governance, administrative, doctrinal, or representative functions on its behalf at the global level.
- F. None of above. chosen
Provenance (1 batch)
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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:28 a.m.