Triple
T4918391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exodus 20:1–17 |
E110401
|
entity |
| Predicate | containsCommandment |
P60020
|
FINISHED |
| Object | You shall have no other gods before me |
—
|
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: You shall have no other gods before me | Statement: [Exodus 20:1–17, containsCommandment, You shall have no other gods before me]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsCommandment Context triple: [Exodus 20:1–17, containsCommandment, You shall have no other gods before me]
-
A.
commandmentType
Indicates the specific category or kind of commandment that an instruction or directive belongs to.
-
B.
numberOfCommandments
Indicates the total count of commandments associated with a given subject.
-
C.
commandmentHebrewName
Indicates the Hebrew-language name assigned to a particular commandment.
-
D.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
-
E.
isCommandedIn
Indicates that an entity is under the authority or control of another entity within a specific context, such as a mission, operation, or organizational structure.
- F. None of above. chosen
Provenance (4 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6fa8be048190892dfaba4d865ee1 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6e482984819087124216738f1e29 |
completed | March 20, 2026, 3:56 p.m. |
Created at: March 20, 2026, 1:29 p.m.