Triple
T208146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Deuteronomy |
E4652
|
entity |
| Predicate | closingEvent |
P4327
|
FINISHED |
| Object | death of Moses |
—
|
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: death of Moses | Statement: [Book of Deuteronomy, closingEvent, death of Moses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closingEvent Context triple: [Book of Deuteronomy, closingEvent, death of Moses]
-
A.
closureAnnouncedBy
Indicates that an entity’s closure has been formally communicated or declared by a specified agent or source.
-
B.
closed
Indicates that an entity has brought something (such as an object, container, or space) from an open state into a shut or sealed state, or that it is currently in that shut state.
-
C.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
D.
concludedAtEvent
chosen
Indicates that an entity’s participation, state, or validity ended as a result of a specific event.
-
E.
closingDoxology
Indicates the concluding liturgical or devotional formula of praise that formally ends a prayer, hymn, or religious text.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e8b9b908190b69a3f0594b95f7e |
completed | Feb. 28, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69a25b4e3c2881908d83e8218aa9f2d9 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.