Triple
T1309274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blessing of Moses |
E27950
|
entity |
| Predicate | precedesText |
P11124
|
FINISHED |
| Object | Death of Moses narrative |
—
|
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 narrative | Statement: [Blessing of Moses, precedesText, Death of Moses narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesText Context triple: [Blessing of Moses, precedesText, Death of Moses narrative]
-
A.
precedesLetter
Indicates that one letter comes immediately before another letter in a specified ordering, such as the alphabet or a given sequence.
-
B.
appearsBefore
chosen
Indicates that one entity occurs, is positioned, or is presented earlier in an ordered sequence than another entity.
-
C.
preludeTo
Indicates that one event, action, or state occurs earlier and serves as an introduction or lead-in to another.
-
D.
pretext
Indicates that one party uses a stated reason or excuse to conceal their true motive for an action or decision.
-
E.
precedentFor
Indicates that one situation, decision, or case serves as an authoritative example or basis for deciding or interpreting another.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c15490a88190872c3d2698a8f9c9 |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4bee9e4a88190b22ab2ee831a23c9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.