Triple
T887473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suffering Servant |
E19161
|
entity |
| Predicate | linkedToNewTestamentPassages |
P3661
|
FINISHED |
| Object | Acts 8:32–35 |
—
|
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 8:32–35 | Statement: [Suffering Servant, linkedToNewTestamentPassages, Acts 8:32–35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToNewTestamentPassages Context triple: [Suffering Servant, linkedToNewTestamentPassages, Acts 8:32–35]
-
A.
textBasisNewTestament
Indicates that a text is based on, derived from, or grounded in the New Testament.
-
B.
textualBasisNewTestament
Indicates that something is based on, derived from, or justified by a text from the New Testament.
-
C.
associatedBiblicalBook
Indicates that one entity is linked or connected to a specific book of the Bible as its relevant or referenced scriptural source.
-
D.
bookNumberInNewTestament
Indicates the numerical position a specific book occupies within the sequence of books in the New Testament.
-
E.
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.
- 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ae787bf081909533082ca013624a |
completed | March 1, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8ff8c48190a33b00acf65c1276 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.