Triple
T34162666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abderus |
E876317
|
entity |
| Predicate | killedByAnimal |
P167491
|
FINISHED |
| Object | man-eating horses |
—
|
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: man-eating horses | Statement: [Abderus, killedByAnimal, man-eating horses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killedByAnimal Context triple: [Abderus, killedByAnimal, man-eating horses]
-
A.
casualtiesAnimal
Indicates that an animal has been harmed, injured, or killed as a result of a particular event or situation.
-
B.
animalFate
chosen
Indicates the outcome or destiny that befalls an animal, such as what ultimately happens to it or how its life concludes.
-
C.
involvedAnimal
Indicates that an animal participates in, is affected by, or is otherwise directly connected to the event or situation described.
-
D.
preyedUpon
Indicates that one entity hunts, attacks, and feeds on another as its prey.
-
E.
wildlifeInteractionType
Indicates the type or nature of interaction occurring between wildlife and another entity (such as humans, other animals, or the environment).
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fdedf708190ab68c2d567e086d0 |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.