Triple
T17868352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meșterul Manole |
E446763
|
entity |
| Predicate | mannerOfDeathInLegend |
P100625
|
FINISHED |
| Object | fall from the monastery roof |
—
|
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: fall from the monastery roof | Statement: [Meșterul Manole, mannerOfDeathInLegend, fall from the monastery roof]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mannerOfDeathInLegend Context triple: [Meșterul Manole, mannerOfDeathInLegend, fall from the monastery roof]
-
A.
legendaryDeath
Indicates a death that is renowned or celebrated in stories or history, often marked by extraordinary circumstances or lasting fame.
-
B.
legendaryCauseOfDeath
chosen
Indicates a legendary or mythic account of how an entity died, as opposed to a historically verified cause of death.
-
C.
deathTypeInFiction
Indicates the manner or category of how a character dies within a fictional narrative.
-
D.
traditionalMannerOfDeath
Indicates that an entity died in a way that follows or reflects a culturally recognized or customary method of death.
-
E.
deifiedPersonDeathCause
Indicates the cause or manner of death of the person who is venerated or treated as a deity.
- 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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49aa0b69081909fba3b42d237b543 |
completed | April 19, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.