Triple
T8827371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortunato |
E210048
|
entity |
| Predicate | settingOfDeath |
P84854
|
FINISHED |
| Object | Italian catacombs |
—
|
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: Italian catacombs | Statement: [Fortunato, settingOfDeath, Italian catacombs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfDeath Context triple: [Fortunato, settingOfDeath, Italian catacombs]
-
A.
effectOfDeath
Indicates the causal impact or consequences that a death has on another entity, state, or process.
-
B.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
C.
hasMannerOfDeath
Indicates the specific way or circumstances in which an entity died, such as natural causes, accident, homicide, or suicide.
-
D.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
E.
deathEpisode
Indicates the episode or event in which an entity’s death occurs or is depicted.
- F. None of above. chosen
Provenance (4 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc6034e8dc819099116d772e87569a |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:47 p.m.