Triple
T34376903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Habakkuk 3:3 |
E882309
|
entity |
| Predicate | parallelThemeWith |
P179644
|
FINISHED |
| Object | Deuteronomy 33:2 |
—
|
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 33:2 | Statement: [Habakkuk 3:3, parallelThemeWith, Deuteronomy 33:2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelThemeWith Context triple: [Habakkuk 3:3, parallelThemeWith, Deuteronomy 33:2]
-
A.
parallelProgram
Indicates that one program or process runs concurrently alongside another, rather than sequentially.
-
B.
parallelSeeTo
Indicates that one entity observes or attends to another entity in a manner that is simultaneous or coordinated with a comparable act of seeing by a different entity.
-
C.
parallelFunctionTo
Indicates that one function corresponds to or mirrors another function in a way that they perform analogous roles or operations, typically in different contexts or systems.
-
D.
parallel
Indicates that two or more entities maintain a constant separation and direction without intersecting or converging.
-
E.
parallelMajor
Indicates that two musical keys share the same tonic note but differ in mode, with one being major and the other minor.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 1:59 a.m.