Triple
T19206358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Thornton |
E480242
|
entity |
| Predicate | deathEffectOn |
P27814
|
FINISHED |
| Object | Buck’s final break with human society |
—
|
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: Buck’s final break with human society | Statement: [John Thornton, deathEffectOn, Buck’s final break with human society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathEffectOn Context triple: [John Thornton, deathEffectOn, Buck’s final break with human society]
-
A.
effectOfDeath
chosen
Indicates the causal impact or consequences that a death has on another entity, state, or process.
-
B.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
-
C.
deathLeadsTo
Indicates that one entity’s death causes, results in, or brings about another event, state, or condition.
-
D.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
E.
damageEffect
Indicates that one entity causes harm, reduction, or deterioration to another entity or its properties.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f99d8ad0819098ebd4ee007149f1 |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:19 p.m.