Triple
T17482096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First U.S. Army Group |
E425685
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional military formation |
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 formation Context triple: [First U.S. Army Group, instanceOf, fictional military formation]
-
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.
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.
-
C.
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.
-
D.
militia-style military formation
A militia-style military formation is an organized group of primarily non-professional, part-time fighters drawn from the civilian population, structured for local defense or irregular warfare under limited formal military hierarchy and training.
-
E.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:48 a.m.