Triple
T14529428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brently Mallard |
E340863
|
entity |
| Predicate | hasDeathEffectOn |
P27814
|
FINISHED |
| Object | Louise Mallard’s emotional state |
—
|
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: Louise Mallard’s emotional state | Statement: [Brently Mallard, hasDeathEffectOn, Louise Mallard’s emotional state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeathEffectOn Context triple: [Brently Mallard, hasDeathEffectOn, Louise Mallard’s emotional state]
-
A.
effectOfDeath
chosen
Indicates the causal impact or consequences that a death has on another entity, state, or process.
-
B.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
-
C.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
D.
deathIs
Indicates that one entity is the cause, manner, or circumstance of another entity’s death.
-
E.
deathResultedIn
Indicates that one event, action, or condition caused or led directly to a particular death as its outcome.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea051bc608190ad4d516c5e7bca43 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.