Triple
T38624681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van Breda family axe murders |
E936972
|
entity |
| Predicate | defenceClaim |
P36520
|
FINISHED |
| Object | intruder attack |
—
|
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: intruder attack | Statement: [Van Breda family axe murders, defenceClaim, intruder attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenceClaim Context triple: [Van Breda family axe murders, defenceClaim, intruder attack]
-
A.
claimsToDefend
Indicates that one entity asserts or professes that its actions or stance are intended to protect or uphold another entity or value.
-
B.
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.
-
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.
defendedOn
Indicates that one entity protected, supported, or argued in favor of another entity during a specific time or event.
-
E.
alsoDefendedIn
Indicates that the same entity or case was defended in an additional context, such as another court, proceeding, or jurisdiction.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:32 p.m.