Triple
T12960224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean-Joachim Goriot |
E310120
|
entity |
| Predicate | causeOfRuin |
P26452
|
FINISHED |
| Object | financial sacrifices for his daughters |
—
|
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: financial sacrifices for his daughters | Statement: [Jean-Joachim Goriot, causeOfRuin, financial sacrifices for his daughters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfRuin Context triple: [Jean-Joachim Goriot, causeOfRuin, financial sacrifices for his daughters]
-
A.
causeOfDownfall
chosen
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
B.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
C.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
D.
causeOfDisaster
Indicates that the subject is responsible for bringing about or triggering the specified disaster.
-
E.
reasonForDemise
Indicates the cause, circumstance, or factor that led to an entity’s death or termination.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:44 p.m.