Triple
T17217409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick |
E417887
|
entity |
| Predicate | neckInjury |
P71097
|
FINISHED |
| Object | partially severed neck |
—
|
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: partially severed neck | Statement: [Nick, neckInjury, partially severed neck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neckInjury Context triple: [Nick, neckInjury, partially severed neck]
-
A.
neckJoint
Indicates a joint or connection located at or functioning as the neck between two body parts or structural elements.
-
B.
injuredBodyPart
chosen
Indicates that an entity has sustained an injury specifically affecting a particular body part.
-
C.
injuryType
Indicates the specific kind or category of injury associated with an entity or event.
-
D.
injuredIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
-
E.
injuriesApprox
Indicates an approximate or estimated number or extent of injuries associated with an event or 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dda6e6c81908dd96f653cd2cba0 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.