Triple
T16034967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curley’s wife |
E388947
|
entity |
| Predicate | deathLeadsTo |
P121683
|
FINISHED |
| Object | the collapse of George and Lennie’s dream |
—
|
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: the collapse of George and Lennie’s dream | Statement: [Curley’s wife, deathLeadsTo, the collapse of George and Lennie’s dream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathLeadsTo Context triple: [Curley’s wife, deathLeadsTo, the collapse of George and Lennie’s dream]
-
A.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
-
B.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
C.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
D.
deathIs
Indicates that one entity is the cause, manner, or circumstance of another entity’s death.
-
E.
deathEpisode
Indicates the episode or event in which an entity’s death occurs or is depicted.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1ff5cd7e481908a29214139a3de2e |
completed | April 17, 2026, 9:37 a.m. |
Created at: April 10, 2026, 4:56 a.m.