Triple
T34376871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deuteronomy 1:1 |
E882308
|
entity |
| Predicate | opensSection |
P80433
|
FINISHED |
| Object | Deuteronomy 1:1–5 |
—
|
NE NERFINISHED |
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 1:1–5 | Statement: [Deuteronomy 1:1, opensSection, Deuteronomy 1:1–5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opensSection Context triple: [Deuteronomy 1:1, opensSection, Deuteronomy 1:1–5]
-
A.
openedSectionBetween
Indicates that one entity has created or established an open section, gap, or interval between itself and another entity.
-
B.
openedWithSection
Indicates that something (such as a document, file, or resource) is opened starting from or via a specific section.
-
C.
openedInSection
Indicates that something was opened or initiated within a specific section or subsection of a larger structure or context.
-
D.
sectionOpened
chosen
Indicates that a particular section has been opened or expanded, making its contents visible or active.
-
E.
openedInSections
Indicates that something has been opened or made accessible in multiple distinct sections or parts.
- 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.