Triple
T1329080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinkel |
E28598
|
entity |
| Predicate | usedForcedLabor |
P27275
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Heinkel, usedForcedLabor, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForcedLabor Context triple: [Heinkel, usedForcedLabor, yes]
-
A.
wasEnslavedIn
Indicates that an entity was held in a state of slavery within a specified place or context.
-
B.
wasFormerlyEnslaved
Indicates that an entity was previously held in a condition of slavery or bondage but is no longer enslaved.
-
C.
usedForImprisoning
Indicates that something serves as a means, tool, or method for confining or detaining someone against their will.
-
D.
legalStatusOfSlavery
Indicates the legal condition or permissibility of slavery within a given jurisdiction, time, or context.
-
E.
populationGroupEnslaved
Indicates that one population group is held in a condition of slavery or forced servitude by another.
- F. None of above. chosen
Provenance (4 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c30c948190afc6342b3dcda948 |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0b1326081909aa6beec0cfe8d6c |
completed | March 1, 2026, 10:41 p.m. |
Created at: March 1, 2026, 7:55 p.m.