Triple
T27286959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sa'd ibn Mu'adh |
E688502
|
entity |
| Predicate | wound |
P28646
|
FINISHED |
| Object | severe injury during Battle of the Trench |
—
|
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: severe injury during Battle of the Trench | Statement: [Sa'd ibn Mu'adh, wound, severe injury during Battle of the Trench]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wound Context triple: [Sa'd ibn Mu'adh, wound, severe injury during Battle of the Trench]
-
A.
woundLocation
Indicates the specific anatomical site on an entity’s body where a wound is present or occurred.
-
B.
woundedAt
Indicates that an entity was injured or harmed at a specific place or during a particular event.
-
C.
actedDespiteWounds
Indicates that an entity performed an action or fulfilled a role even though it was wounded or injured at the time.
-
D.
wasWoundedIn
chosen
Indicates that an entity sustained an injury as a result of a specified event, situation, or conflict.
-
E.
winding
Indicates that something follows a curving, twisting, or spiral path or shape rather than a straight one.
- 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_69f627565c688190a8f4f9fd9ce84990 |
completed | May 2, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:12 a.m.