Triple
T21103976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terce |
E519989
|
entity |
| Predicate | linkedToBiblicalVerse |
P114904
|
FINISHED |
| Object | Acts 2:15 |
—
|
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: Acts 2:15 | Statement: [Terce, linkedToBiblicalVerse, Acts 2:15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToBiblicalVerse Context triple: [Terce, linkedToBiblicalVerse, Acts 2:15]
-
A.
associatedWithBiblicalChapter
Indicates that something has a specified connection or linkage to a particular chapter in the Bible.
-
B.
scripturalReference
Indicates that one entity cites, alludes to, or is based on a specific passage or portion of a scriptural text found in another entity.
-
C.
associatedWithVerse
chosen
Indicates a relationship where something is linked or connected to a specific verse, typically in a text or scripture.
-
D.
associatedBiblicalBook
Indicates that one entity is linked or connected to a specific book of the Bible as its relevant or referenced scriptural source.
-
E.
linkedToGospel
Indicates a relationship where something is connected or related to the gospel, typically in content, origin, or thematic focus.
- 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b6050e481908a5e48b667ac1503 |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:53 p.m.