Triple
T3538533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chuck Hansen |
E74824
|
entity |
| Predicate | sacrificesSelf |
P18946
|
FINISHED |
| Object | to help destroy the Breach |
—
|
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: to help destroy the Breach | Statement: [Chuck Hansen, sacrificesSelf, to help destroy the Breach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacrificesSelf Context triple: [Chuck Hansen, sacrificesSelf, to help destroy the Breach]
-
A.
sacrifice
chosen
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
-
B.
sacrificeType
Indicates the specific kind or category of sacrifice involved in a sacrificial action or relationship.
-
C.
sacrificeAcceptedBy
Indicates that a sacrificial offering made by one entity is received and deemed acceptable by another entity.
-
D.
sacrificeLocation
Indicates the place where a sacrifice is performed or occurs.
-
E.
ultimatelyRefusesToKill
Indicates that an entity, despite prior opportunity or intent, finally decides not to kill another entity.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbcca5e008190abcfe40c8902a95f |
completed | March 8, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.