Triple
T34376857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deuteronomy 1:1 |
E882308
|
entity |
| Predicate | setsSceneFor |
P82145
|
FINISHED |
| Object | historical review in Deuteronomy 1–4 |
—
|
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: historical review in Deuteronomy 1–4 | Statement: [Deuteronomy 1:1, setsSceneFor, historical review in Deuteronomy 1–4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsSceneFor Context triple: [Deuteronomy 1:1, setsSceneFor, historical review in Deuteronomy 1–4]
-
A.
setsStageFor
chosen
Indicates that one event, condition, or action creates the necessary circumstances or groundwork for another to occur.
-
B.
isSettingOfScene
Indicates that a particular location, time, or environment serves as the backdrop or context in which a scene takes place.
-
C.
showsScene
Indicates that one entity (such as a media item or visual representation) depicts or presents a particular scene.
-
D.
centralScene
Indicates that one scene functions as the main or focal scene within a larger narrative, sequence, or composition.
-
E.
scenes
Indicates that one entity is a scene or setting in which the other entity occurs, appears, or is depicted.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.