Triple
T3083263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Arellano |
E64306
|
entity |
| Predicate | injuryCause |
P14656
|
FINISHED |
| Object | blow to the abdomen during a match in Valladolid |
—
|
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: blow to the abdomen during a match in Valladolid | Statement: [David Arellano, injuryCause, blow to the abdomen during a match in Valladolid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: injuryCause Context triple: [David Arellano, injuryCause, blow to the abdomen during a match in Valladolid]
-
A.
causeOfInjury
chosen
Indicates that one entity is the source or reason that another entity sustained an injury.
-
B.
injuryType
Indicates the specific kind or category of injury associated with an entity or event.
-
C.
injuriesApprox
Indicates an approximate or estimated number or extent of injuries associated with an event or entity.
-
D.
resultOfAccident
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
E.
accidentType
Indicates the specific category or kind of accident associated with an event or incident.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1e877008190aacbd6f1357bdb9b |
completed | March 8, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.