Triple
T37716544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sad Sack |
E939466
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional United States Army personnel |
C7744
|
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 United States Army personnel Context triple: [Sad Sack, instanceOf, fictional United States Army personnel]
-
A.
fictional United States Army unit
A fictional United States Army unit is an imagined military formation, typically created for storytelling or simulation, that reflects the structure, culture, and missions of real Army units while allowing narrative flexibility and creative license.
-
B.
World War II fiction characters
World War II fiction characters are imagined individuals whose lives, actions, and relationships are shaped by the historical events, settings, and moral complexities of the Second World War.
-
C.
fictional French officer
A fictional French officer is an imagined military character, typically serving in France’s armed forces, whose rank, personality, and actions drive narratives set in historical or invented conflicts.
-
D.
American military personnel
chosen
American military personnel are individuals who serve in the United States Armed Forces, including the Army, Navy, Air Force, Marine Corps, Space Force, and Coast Guard, in roles ranging from combat and support to technical and administrative duties.
-
E.
fictionalCharacter
A fictionalCharacter is an invented person or being in a narrative work, defined by attributes, relationships, and actions that drive the story and embody its themes.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.