Triple
T26988023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carl Grimes |
E679784
|
entity |
| Predicate | causeOfEyeInjury |
P89605
|
FINISHED |
| Object | gunshot wound to the head |
—
|
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: gunshot wound to the head | Statement: [Carl Grimes, causeOfEyeInjury, gunshot wound to the head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfEyeInjury Context triple: [Carl Grimes, causeOfEyeInjury, gunshot wound to the head]
-
A.
causeOfInjury
Indicates that one entity is the source or reason that another entity sustained an injury.
-
B.
eyeConditionCause
chosen
Indicates that one factor or event is the cause or contributing cause of a particular eye-related condition or disorder.
-
C.
eyesPutOutBy
Indicates that one entity has caused another entity’s eyes to be damaged or removed, resulting in blindness.
-
D.
injuryType
Indicates the specific kind or category of injury associated with an entity or event.
-
E.
eyeCondition
Indicates that an entity has, experiences, or is characterized by a particular condition or disorder affecting the eyes.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 6:50 a.m.