Triple
T28950821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medraut |
E731009
|
entity |
| Predicate | fatallyWounds |
P62389
|
FINISHED |
| Object | KingArthur |
—
|
NE NERFINISHED |
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: KingArthur | Statement: [Medraut, fatallyWounds, KingArthur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fatallyWounds Context triple: [Medraut, fatallyWounds, KingArthur]
-
A.
fatalInjury
Indicates that an entity causes or sustains an injury that directly results in death.
-
B.
fatallyDamaged
Indicates that an entity has been harmed or impaired to such an extent that death is inevitable or has already occurred as a result of the damage.
-
C.
killedOrMortallyWounded
chosen
Indicates that one entity caused the death of, or inflicted injuries certain to result in the death of, another entity.
-
D.
woundedAt
Indicates that an entity was injured or harmed at a specific place or during a particular event.
-
E.
wasDeadly
Indicates that an event, action, or condition resulted in death or had the capacity to cause death.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65bb81a548190b34758aa480a8f11 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:43 a.m.