Triple
T33724475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian military tribunals |
E864104
|
entity |
| Predicate | triesOffenseType |
P177650
|
FINISHED |
| Object | military crimes |
—
|
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: military crimes | Statement: [Italian military tribunals, triesOffenseType, military crimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triesOffenseType Context triple: [Italian military tribunals, triesOffenseType, military crimes]
-
A.
attemptStyle
Indicates the manner or approach with which an entity attempts to perform an action or achieve a goal.
-
B.
temptsCharacter
Indicates that one character attempts to lure, entice, or persuade another character toward a particular action, choice, or desire, often involving moral or personal conflict.
-
C.
canTry
Indicates that an entity has the possibility or permission to attempt performing a particular action or achieving a certain outcome.
-
D.
triesToUse
Indicates an entity’s attempt or effort to make use of another entity, regardless of whether the use is successful.
-
E.
attemptNumber
Indicates the specific ordinal count of attempts made for a given action or process.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:44 a.m.