Triple
T4767652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hosea 11:1 |
E105850
|
entity |
| Predicate | scriptureReference |
P3661
|
FINISHED |
| Object | Hos 11:1 |
—
|
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: Hos 11:1 | Statement: [Hosea 11:1, scriptureReference, Hos 11:1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptureReference Context triple: [Hosea 11:1, scriptureReference, Hos 11:1]
-
A.
scripturalReference
chosen
Indicates that one entity cites, alludes to, or is based on a specific passage or portion of a scriptural text found in another entity.
-
B.
scriptureFor
Indicates that one entity serves as a scriptural or authoritative religious text for another entity (such as a person, group, or belief system).
-
C.
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.
-
D.
scriptureFocus
Indicates that something centers on, emphasizes, or is primarily concerned with religious scripture or sacred texts.
-
E.
scripturalBasis
Indicates that one entity serves as the religious or scriptural foundation, support, or justification for another entity (such as a belief, practice, or doctrine).
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.