Triple
T32266764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zintani armed coalitions |
E824307
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | armed group network |
C42817
|
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 group network Context triple: [Zintani armed coalitions, instanceOf, armed group network]
-
A.
Apache group
A group of Apache is a collection of Apache HTTP server processes or instances that work together to handle web requests, often configured for load balancing, redundancy, or distributed hosting.
-
B.
tribal network
A tribal network is a loosely organized, trust-based community of individuals or groups connected by shared identity, values, or purpose, who collaborate and exchange resources through informal, often decentralized relationships.
-
C.
alliance of armed groups
chosen
An alliance of armed groups is a cooperative association of distinct militant or paramilitary organizations that coordinate strategies, resources, and operations to pursue shared political, ideological, or territorial objectives.
-
D.
hunter-killer group
A hunter-killer group is a coordinated military formation, typically composed of surface ships, submarines, or aircraft, organized to locate, track, and destroy enemy submarines or other high-value targets.
-
E.
military base network
A military base network is an interconnected system of communication, data, and operational infrastructure linking facilities, units, and resources across one or more military installations to support command, control, logistics, and security functions.
- F. None of above.
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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:42 a.m.