Triple
T14060582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uriah son of Shemaiah |
E338332
|
entity |
| Predicate | bodyDisposedAt |
P111116
|
FINISHED |
| Object | graves of the common people |
—
|
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: graves of the common people | Statement: [Uriah son of Shemaiah, bodyDisposedAt, graves of the common people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyDisposedAt Context triple: [Uriah son of Shemaiah, bodyDisposedAt, graves of the common people]
-
A.
bodyDisposedIn
Indicates that a body (typically a dead organism or corpse) is placed, discarded, or otherwise disposed of within a particular location or container.
-
B.
bodyPartBuriedAt
Indicates that a specific body part of an entity is interred or laid to rest at a particular location.
-
C.
dissipatedOn
Indicates that something (such as energy, force, or a substance) is dispersed, lost, or converted into a less usable form on or within a particular medium, surface, or system.
-
D.
bodyFinish
Indicates that one entity completes or finishes the main body or primary portion of another entity.
-
E.
bodyBuriedAt
chosen
Indicates that the physical remains of an entity are interred or concealed at a specific location.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5686f51c81908c33143ecbaae83d |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.