Triple
T75617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SovietPrisonersOfWar |
E1511
|
entity |
| Predicate | treatment |
P4714
|
FINISHED |
| Object | extremeBrutality |
—
|
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: extremeBrutality | Statement: [SovietPrisonersOfWar, treatment, extremeBrutality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatment Context triple: [SovietPrisonersOfWar, treatment, extremeBrutality]
-
A.
remedySought
Indicates that a particular legal or corrective action is being requested as a solution or relief in response to a problem or dispute.
-
B.
traction
Indicates the degree to which one entity’s movement or influence effectively grips, pulls, or gains momentum relative to another entity or medium.
-
C.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
D.
treaty
Indicates a formal, negotiated agreement or pact established between entities, typically states or organizations, that defines mutual obligations, rights, or terms of cooperation.
-
E.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a25314bd6c81908d1cfd4b83f20049 |
completed | Feb. 28, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69a24eae77ec81909015906f31f2b62e |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a25313f1688190ba0fa8677faaf65b |
completed | Feb. 28, 2026, 2:29 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.