Triple
T34089233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | And the Shofar Blew |
E874257
|
entity |
| Predicate | hasChristianDoctrineElements |
P181375
|
FINISHED |
| Object | repentance |
—
|
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: repentance | Statement: [And the Shofar Blew, hasChristianDoctrineElements, repentance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChristianDoctrineElements Context triple: [And the Shofar Blew, hasChristianDoctrineElements, repentance]
-
A.
hasTheologicalElement
chosen
Indicates that something includes, expresses, or is characterized by a theological aspect, theme, or component.
-
B.
hasDoctrinalBasis
Indicates that one concept, claim, or practice is grounded in, supported by, or derived from a specific doctrine or set of doctrines.
-
C.
hasEucharisticDoctrine
Indicates that an entity holds, teaches, or is characterized by a particular doctrine or set of beliefs about the Eucharist.
-
D.
hasDoctrinalCharacteristic
Indicates that an entity possesses a specific doctrinal feature, quality, or attribute within a belief or teaching system.
-
E.
hasNumberOfDoctrines
Indicates the relationship that specifies how many doctrines are associated with a given 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 1, 2026, 1:52 a.m.