Triple
T1681296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War Criminals Prison No. 1 |
E36343
|
entity |
| Predicate | hasExecutionMethod |
P2301
|
FINISHED |
| Object | hanging |
—
|
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: hanging | Statement: [War Criminals Prison No. 1, hasExecutionMethod, hanging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExecutionMethod Context triple: [War Criminals Prison No. 1, hasExecutionMethod, hanging]
-
A.
hasWorkingMethod
Indicates that one entity possesses or employs a functional method, procedure, or technique to achieve a particular task or outcome.
-
B.
hasExecutor
Indicates that a particular action, task, or legal instrument is carried out or implemented by a specified responsible agent or party.
-
C.
hasMethodType
Indicates that an entity is associated with, or characterized by, a specific type or category of method used or applied in its context.
-
D.
executedWith
chosen
Indicates that an action or process was carried out using, accompanied by, or in conjunction with a specified tool, method, or participant.
-
E.
hasCalledProgram
Indicates that one program has invoked or executed another program.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.