Triple
T35647099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juliet Delos |
E1030040
|
entity |
| Predicate | deathInfluences |
P27814
|
FINISHED |
| Object | William's descent into darkness |
—
|
NE NERFINISHED |
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: William's descent into darkness | Statement: [Juliet Delos, deathInfluences, William's descent into darkness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathInfluences Context triple: [Juliet Delos, deathInfluences, William's descent into darkness]
-
A.
deathPlaceInfluence
Indicates that the place where an entity died had a significant impact or influence on that entity or its legacy.
-
B.
effectOfDeath
chosen
Indicates the causal impact or consequences that a death has on another entity, state, or process.
-
C.
riskFactorForDeath
Indicates that something increases the likelihood or probability of death occurring.
-
D.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
E.
featuresDeath
Indicates that the subject includes, depicts, or involves a death or deaths as a notable element.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:05 p.m.