Triple
T28640055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niobe in Rome |
E724894
|
entity |
| Predicate | deathTriggeredBy |
P54491
|
FINISHED |
| Object | revelation of her son’s true paternity |
—
|
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: revelation of her son’s true paternity | Statement: [Niobe in Rome, deathTriggeredBy, revelation of her son’s true paternity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathTriggeredBy Context triple: [Niobe in Rome, deathTriggeredBy, revelation of her son’s true paternity]
-
A.
deathTriggers
Indicates that the occurrence of one entity’s death causes or initiates another event, state, or process.
-
B.
deathBy
chosen
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
C.
deathResultedIn
Indicates that one event, action, or condition caused or led directly to a particular death as its outcome.
-
D.
deathInterpretedAs
Indicates that one entity’s death is understood, framed, or interpreted in a particular way by another entity or within a given context.
-
E.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 4:43 a.m.