Triple
T17269447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicodemus |
E419213
|
entity |
| Predicate | burialSpicesWeight |
P121622
|
FINISHED |
| Object | about seventy-five pounds (about a hundred Roman litrai) |
—
|
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: about seventy-five pounds (about a hundred Roman litrai) | Statement: [Nicodemus, burialSpicesWeight, about seventy-five pounds (about a hundred Roman litrai)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialSpicesWeight Context triple: [Nicodemus, burialSpicesWeight, about seventy-five pounds (about a hundred Roman litrai)]
-
A.
buriedWith
Indicates that one entity is interred in the same grave, tomb, or burial site as another entity.
-
B.
hasBurialCustoms
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
-
C.
usedForBurialOf
Indicates that something serves or is employed as a means, place, or object for burying a particular entity.
-
D.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
E.
burialDetail
chosen
Indicates details about how, where, and under what circumstances an 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4803b48190894b3bb9a4970602 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.