Triple
T20613605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarah (Book of Tobit) |
E506508
|
entity |
| Predicate | reasonForDespair |
P140774
|
FINISHED |
| Object | reproach from a maid |
—
|
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: reproach from a maid | Statement: [Sarah (Book of Tobit), reasonForDespair, reproach from a maid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDespair Context triple: [Sarah (Book of Tobit), reasonForDespair, reproach from a maid]
-
A.
disillusionedBy
Indicates that one entity has lost trust, faith, or idealistic belief as a result of the actions, behavior, or nature of another entity.
-
B.
reasonForDemise
Indicates the cause, circumstance, or factor that led to an entity’s death or termination.
-
C.
downfall
Indicates the process or event by which an entity experiences a significant decline, ruin, or loss of power, status, or success.
-
D.
decline
Indicates a decrease or reduction in the level, amount, quality, or intensity of something over time.
-
E.
deathMotivation
Indicates a relationship where one entity’s death serves as the reason, cause, or motivating factor for another entity’s actions or state.
- F. None of above. chosen
Provenance (4 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aada19e481909363428ceda67603 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:41 a.m.