Triple
T26394294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ada Monroe |
E663503
|
entity |
| Predicate | afterFatherDeath |
P126199
|
FINISHED |
| Object | left alone to manage the farm |
—
|
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: left alone to manage the farm | Statement: [Ada Monroe, afterFatherDeath, left alone to manage the farm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterFatherDeath Context triple: [Ada Monroe, afterFatherDeath, left alone to manage the farm]
-
A.
afterDeathOf
chosen
Indicates that one event, state, or condition occurs subsequent to and as a result of the death of a specified entity.
-
B.
releasedAfterDeathOf
Indicates that something (such as a work, product, or announcement) was released only after the death of a specified person.
-
C.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
D.
canonicalDeathOfFather
Indicates that the referenced death event is the officially recognized or primary recorded death of the subject’s father.
-
E.
continuedAfterDeathOf
Indicates that an action, state, or process persisted beyond and despite the death of a specified 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 11:27 p.m.