Triple
T4748279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exodus 13:16 |
E105414
|
entity |
| Predicate | parallelPassageWith |
P51251
|
FINISHED |
| Object | Deuteronomy 6:8 |
—
|
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: Deuteronomy 6:8 | Statement: [Exodus 13:16, parallelPassageWith, Deuteronomy 6:8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelPassageWith Context triple: [Exodus 13:16, parallelPassageWith, Deuteronomy 6:8]
-
A.
parallelPassage
chosen
Indicates that one text segment corresponds closely in content or structure to another, such that they can be considered parallel versions or accounts of the same material.
-
B.
parallelCorridorFor
Indicates that one corridor runs alongside and in the same general direction as another corridor, forming a parallel passage.
-
C.
parallelEvent
Indicates that two or more events occur at the same time or overlap in time without a required order between them.
-
D.
followsParallel
Indicates that one entity proceeds in the same general direction or sequence as another, maintaining a parallel course or progression without necessarily intersecting.
-
E.
parallelGospel
Indicates that one gospel text corresponds closely to another in content, structure, or narrative, allowing them to be compared side by side as parallel accounts.
- 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64c567288190a420e6825ee72822 |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.