Triple
T31269173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary of Cana |
E797335
|
entity |
| Predicate | gospelReference |
P3661
|
FINISHED |
| Object | Gospel of John 2:1–11 |
—
|
NE NERFINISHED |
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: Gospel of John 2:1–11 | Statement: [Sanctuary of Cana, gospelReference, Gospel of John 2:1–11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gospelReference Context triple: [Sanctuary of Cana, gospelReference, Gospel of John 2:1–11]
-
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.
gospelChapter
Indicates that one entity is a specific chapter within a particular gospel text or book.
-
C.
gospelTerm
Indicates that one entity is a term, concept, or expression specifically associated with the gospel or gospel-related discourse in relation to another entity.
-
D.
gospelLocation
Indicates the location where a gospel-related event, activity, or presence occurs or is associated.
-
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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:13 p.m.