Triple
T27280891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwight (The Walking Dead) |
E688326
|
entity |
| Predicate | causeOfScar |
P14656
|
FINISHED |
| Object | burned with a hot iron by Negan |
—
|
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: burned with a hot iron by Negan | Statement: [Dwight (The Walking Dead), causeOfScar, burned with a hot iron by Negan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfScar Context triple: [Dwight (The Walking Dead), causeOfScar, burned with a hot iron by Negan]
-
A.
causeOfInjury
chosen
Indicates that one entity is the source or reason that another entity sustained an injury.
-
B.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
causeStatus
Indicates that one entity brings about, initiates, or is responsible for a particular state or condition in another entity.
-
D.
causeInStory
Indicates that one event, action, or state functions as the cause of another within the narrative structure of a story.
-
E.
bodyModificationReason
Indicates the reason or motivation behind a particular body modification performed on an 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 11:07 a.m.