Triple
T1992298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen |
E43276
|
entity |
| Predicate | buriedBy |
P30812
|
FINISHED |
| Object | devout men who made great lamentation over him |
—
|
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: devout men who made great lamentation over him | Statement: [Stephen, buriedBy, devout men who made great lamentation over him]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buriedBy Context triple: [Stephen, buriedBy, devout men who made great lamentation over him]
-
A.
buriedWith
Indicates that one entity is interred in the same grave, tomb, or burial site as another entity.
-
B.
burialBy
chosen
Indicates that one entity is responsible for burying or interring another entity.
-
C.
notBuriedHere
Indicates that the entity in question is explicitly not buried at the specified location.
-
D.
burials
Indicates that one entity is interred or laid to rest in a grave or burial site associated with another entity.
-
E.
burialText
Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8ee02dc81908fec9fd8df7a4f40 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb79ad6888190be99943a9c73cf3e |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.