Triple

T24922201
Position Surface form Disambiguated ID Type / Status
Subject Deuteronomy 32 E618758 entity
Predicate containsVerse P28117 FINISHED
Object Deuteronomy 32:15
Deuteronomy 32:15 is a verse in the Old Testament’s “Song of Moses” that poetically rebukes Israel for growing complacent and unfaithful after experiencing God’s blessings.
E1656163 NE 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: Deuteronomy 32:15 | Statement: [Deuteronomy 32, containsVerse, Deuteronomy 32:15]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Deuteronomy 32:15
Triple: [Deuteronomy 32, containsVerse, Deuteronomy 32:15]
Generated description
Deuteronomy 32:15 is a verse in the Old Testament’s “Song of Moses” that poetically rebukes Israel for growing complacent and unfaithful after experiencing God’s blessings.

Provenance (5 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_69e2fab9edd88190b86004a78a28bc20 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f423919c248190b87446ae2043f15a completed May 1, 2026, 3:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a103332581c81908e35c5a73b23b758 completed May 22, 2026, 10:42 a.m.
NEDg Description generation batch_6a1033eeacac81909e208f3b3e17190e completed May 22, 2026, 10:46 a.m.
NED2 Entity disambiguation (via description) batch_6a1034c45fb88190865f904fd8e766b3 completed May 22, 2026, 10:49 a.m.
Created at: April 18, 2026, 5:29 a.m.