Triple
T19299241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exodus 19 |
E482648
|
entity |
| Predicate | containsResponse |
P40030
|
FINISHED |
| Object | people’s promise to do all that the Lord has spoken |
—
|
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: people’s promise to do all that the Lord has spoken | Statement: [Exodus 19, containsResponse, people’s promise to do all that the Lord has spoken]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsResponse Context triple: [Exodus 19, containsResponse, people’s promise to do all that the Lord has spoken]
-
A.
includesResponse
chosen
Indicates that one entity contains, incorporates, or encompasses another entity as a response or reply.
-
B.
usesResponseCode
Indicates that one entity produces, returns, or relies on a particular response code as part of its behavior or interaction.
-
C.
requiresResponse
Indicates that an action, event, or communication necessitates a reply or follow-up response from another party.
-
D.
hasNotableResponse
Indicates that an entity has received a significant, noteworthy, or widely recognized reaction or feedback in response to it.
-
E.
responseFrom
Indicates that one entity is the originator or source of a response directed to another entity or request.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc8852208190ba0337a9623d9bdf |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.