Triple
T23752368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gospel of Luke 23:38 |
E587003
|
entity |
| Predicate | verseAfter |
P153556
|
FINISHED |
| Object | Gospel of Luke 23:39 |
—
|
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 Luke 23:39 | Statement: [Gospel of Luke 23:38, verseAfter, Gospel of Luke 23:39]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verseAfter Context triple: [Gospel of Luke 23:38, verseAfter, Gospel of Luke 23:39]
-
A.
verse
Indicates that one entity is in opposition or conflict against another, as in a competitive or adversarial relationship.
-
B.
verse3
Indicates a relationship where one entity is the third verse or stanza associated with another entity, such as a song, poem, or scripture passage.
-
C.
verse2
Indicates that one entity is the second verse or stanza associated with another entity, typically within a structured text like a song, poem, or scripture.
-
D.
verses
Indicates a relationship where one entity competes or is pitted against another, as in an opposition, matchup, or comparison.
-
E.
verseNumber
Indicates the specific numbered position of a verse within an ordered sequence, such as in a chapter, song, or poem.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcc3a06c81908e8a6e1f531c73bc |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:13 p.m.