Triple
T1766455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commissar Order |
E38773
|
entity |
| Predicate | implementationCharacter |
P31661
|
FINISHED |
| Object | criminal implementation of warfare |
—
|
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: criminal implementation of warfare | Statement: [Commissar Order, implementationCharacter, criminal implementation of warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementationCharacter Context triple: [Commissar Order, implementationCharacter, criminal implementation of warfare]
-
A.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
B.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
C.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
D.
basedOnCharacterBy
Indicates that one work, adaptation, or portrayal is derived from or inspired by a character created by another entity.
-
E.
regionCharacter
Indicates a characteristic, feature, or quality that typifies or defines a particular region.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab39faf69c8190bae98d3e3911078f |
completed | March 6, 2026, 8:32 p.m. |
Created at: March 4, 2026, 7:31 p.m.