Triple
T19784564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rechab son of Rimmon |
E475225
|
entity |
| Predicate | postmortemTreatment |
P112223
|
FINISHED |
| Object | body hanged beside the pool in Hebron |
—
|
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: body hanged beside the pool in Hebron | Statement: [Rechab son of Rimmon, postmortemTreatment, body hanged beside the pool in Hebron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postmortemTreatment Context triple: [Rechab son of Rimmon, postmortemTreatment, body hanged beside the pool in Hebron]
-
A.
posthumousAction
chosen
Indicates an action or event that occurs or is carried out after the death of the person to whom it relates.
-
B.
posthumousDiagnosis
Indicates that a diagnosis was made for an individual only after their death.
-
C.
posthumousForm
Indicates a form, version, or representation of something that is created, recognized, or exists only after the death of the associated entity.
-
D.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
E.
cremation
Indicates that one entity performs or undergoes the process of reducing a dead body to ashes by burning.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538715b8819080c6930e7d16ab58 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.