Triple
T11241940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis 25 |
E266091
|
entity |
| Predicate | locatesBurialIn |
P196
|
FINISHED |
| Object | field purchased from Ephron the Hittite |
—
|
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: field purchased from Ephron the Hittite | Statement: [Genesis 25, locatesBurialIn, field purchased from Ephron the Hittite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatesBurialIn Context triple: [Genesis 25, locatesBurialIn, field purchased from Ephron the Hittite]
-
A.
buriedNear
Indicates that one entity is interred or buried in close physical proximity to another entity.
-
B.
burialCoordinates
Indicates the geographic location where an entity is buried, typically expressed as spatial coordinates.
-
C.
tombLocatedIn
Indicates that a particular tomb is situated within or at a specified location or place.
-
D.
isBuriedIn
Indicates that one entity is located beneath the ground or enclosed within another entity, typically as in a grave, tomb, or burial site.
-
E.
burialPlace
chosen
Indicates the location where a person or entity is buried.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e919eaf48190a1457851cfc56afb |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d7878906f48190b63ddc103a0c8f9b |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:30 p.m.