Triple
T33343642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zubrowkan military police |
E853737
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional military police force |
C4374
|
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: fictional military police force Context triple: [Zubrowkan military police, instanceOf, fictional military police force]
-
A.
fictional military program
A fictional military program is an imagined, often secretive initiative or project within an armed forces setting, designed to explore advanced technologies, strategies, or operations that drive the narrative in speculative or military-themed stories.
-
B.
paramilitary organization
A paramilitary organization is a structured group that operates with military-style training, hierarchy, and tactics but is not formally part of a recognized state's official armed forces.
-
C.
fictional political institution
A fictional political institution is an imagined organization or governing body within a narrative world that creates, interprets, or enforces rules, policies, or power structures for story purposes.
-
D.
fictional group
chosen
A fictional group is an imagined collection of characters or entities, defined by shared traits, goals, or context, that exists only within a narrative or creative work.
-
E.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:34 a.m.