Triple
T6124244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Calley |
E136555
|
entity |
| Predicate | statedDefense |
P36520
|
FINISHED |
| Object | claimed he was following orders |
—
|
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: claimed he was following orders | Statement: [William Calley, statedDefense, claimed he was following orders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statedDefense Context triple: [William Calley, statedDefense, claimed he was following orders]
-
A.
defendedAs
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
-
B.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
C.
defenseArgument
chosen
Indicates that an entity presents or supports a line of reasoning intended to defend or justify another entity, often in a legal or argumentative context.
-
D.
typeOfDefense
Indicates the specific kind or category of defense employed or possessed in a given context.
-
E.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05c25976081909e0a40e07dff0b8a |
completed | March 22, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.