Triple
T9965352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roderick Usher |
E195668
|
entity |
| Predicate | deathAssociatedWith |
P54491
|
FINISHED |
| Object | collapse of the House of Usher |
—
|
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: collapse of the House of Usher | Statement: [Roderick Usher, deathAssociatedWith, collapse of the House of Usher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathAssociatedWith Context triple: [Roderick Usher, deathAssociatedWith, collapse of the House of Usher]
-
A.
deathCharacteristic
Indicates a characteristic, attribute, or quality specifically associated with a death event or the manner in which death occurred.
-
B.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
C.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
-
D.
deathResultedIn
Indicates that one event, action, or condition caused or led directly to a particular death as its outcome.
-
E.
deathBy
chosen
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb71c38488190a6f3cda11994f6a2 |
completed | April 2, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.