Triple
T31857815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Canon |
E813243
|
entity |
| Predicate | usesBiblicalAllusions |
P3890
|
FINISHED |
| Object | Old Testament |
—
|
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: Old Testament | Statement: [Great Canon, usesBiblicalAllusions, Old Testament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBiblicalAllusions Context triple: [Great Canon, usesBiblicalAllusions, Old Testament]
-
A.
scripturalAllusion
Indicates that one entity references, echoes, or draws upon content, themes, or language from a scriptural or sacred text in relation to another entity.
-
B.
scriptureAllusion
Indicates that one entity makes reference to, echoes, or is inspired by a passage, theme, or element from a scriptural text found in another entity.
-
C.
containsAllusion
Indicates that one entity includes or incorporates an indirect reference or allusion to another entity.
-
D.
hasBiblicalConnection
chosen
Indicates a relationship in which one entity is connected to another through references, themes, origins, or influences derived from the Bible.
-
E.
scripturalUse
Indicates that one entity is used as a scriptural reference, source, or basis within the context or content of another entity.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 30, 2026, 11:52 p.m.