Triple
T3641864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gustloff-Werk II subcamp |
E77205
|
entity |
| Predicate | workAssigned |
P3151
|
FINISHED |
| Object | armaments production |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: armaments production | Statement: [Gustloff-Werk II subcamp, workAssigned, armaments production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workAssigned Context triple: [Gustloff-Werk II subcamp, workAssigned, armaments production]
-
A.
assignedTo
chosen
Indicates that responsibility for a task, item, or role has been designated to a specific entity.
-
B.
assignedInStandard
Indicates that something is allocated or designated within a defined standard, specification, or normative framework.
-
C.
assignedUnder
Indicates that one entity has been given responsibility, duty, or authority to act within the scope, supervision, or framework defined by another entity.
-
D.
workDistributor
Indicates that one entity is responsible for assigning, allocating, or distributing work or tasks to others.
-
E.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
- F. None of above.
Provenance (3 batches)
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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc359a91481908aef1c022f45e55c |
completed | March 8, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.