Triple
T8227207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnaeus Pompeius Strabo |
E192201
|
entity |
| Predicate | manner of death |
P48923
|
FINISHED |
| Object | died of illness |
—
|
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: died of illness | Statement: [Gnaeus Pompeius Strabo, manner of death, died of illness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manner of death Context triple: [Gnaeus Pompeius Strabo, manner of death, died of illness]
-
A.
allegedMannerOfDeath
Indicates that the specified manner of death is claimed or reported for an entity, but not confirmed as factual.
-
B.
hasMannerOfDeath
chosen
Indicates the specific way or circumstances in which an entity died, such as natural causes, accident, homicide, or suicide.
-
C.
hasMannerOfDeathOfVictim
Indicates the specific way or circumstances in which the victim died in relation to the event or action being described.
-
D.
traditionalMannerOfDeath
Indicates that an entity died in a way that follows or reflects a culturally recognized or customary method of death.
-
E.
hasPartInMannerOfDeath
Indicates that an entity’s involvement in a death is characterized or qualified by a specific manner or way in which the death occurred.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb77fdcb048190868ea4995b020a37 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.