Triple
T32201239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stalingrad prisoner-of-war camp |
E822541
|
entity |
| Predicate | conditionOfImprisonment |
P50529
|
FINISHED |
| Object | harsh |
—
|
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: harsh | Statement: [Stalingrad prisoner-of-war camp, conditionOfImprisonment, harsh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionOfImprisonment Context triple: [Stalingrad prisoner-of-war camp, conditionOfImprisonment, harsh]
-
A.
detentionCondition
chosen
Indicates the specific terms, circumstances, or requirements under which a person is held in detention.
-
B.
manyPrisonersCondition
Indicates a situation in which a large number of individuals are held in prison or detention, emphasizing the condition of having many prisoners.
-
C.
durationOfImprisonment
Indicates the length of time that an entity is or was held in imprisonment.
-
D.
sometimesImprisons
Indicates that one entity occasionally confines or incarcerates another entity, but not on a regular or constant basis.
-
E.
imprisonmentContext
Indicates that one entity is held in confinement or custody by another entity or authority within a specific legal, temporal, or situational context.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:36 a.m.