Triple
T3720258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coniah |
E81620
|
entity |
| Predicate | scripturalCurse |
P51411
|
FINISHED |
| Object | Jeremiah 22:30 |
—
|
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: Jeremiah 22:30 | Statement: [Coniah, scripturalCurse, Jeremiah 22:30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturalCurse Context triple: [Coniah, scripturalCurse, Jeremiah 22:30]
-
A.
associatedCurse
Indicates that one entity is linked to, affected by, or bears responsibility for a particular curse related to another entity.
-
B.
attemptedCurseReversal
Indicates an action where one entity tried, but did not necessarily succeed, to reverse or undo a curse affecting another entity.
-
C.
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.
-
D.
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.
-
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. 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca9b5ca8819094299fffc02606ce |
completed | March 8, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc48ec1a081909af0ff9f267c0ffe |
completed | March 8, 2026, 6:48 p.m. |
Created at: March 8, 2026, 3:34 p.m.