Triple
T28781072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galatians 6:2 |
E726677
|
entity |
| Predicate | neighborVerseNext |
P122361
|
FINISHED |
| Object | Galatians 6:3 |
—
|
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: Galatians 6:3 | Statement: [Galatians 6:2, neighborVerseNext, Galatians 6:3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighborVerseNext Context triple: [Galatians 6:2, neighborVerseNext, Galatians 6:3]
-
A.
verseAfter
Indicates that one verse occurs immediately later in sequence than another verse within the same ordered text.
-
B.
neighboringVersePrevious
Indicates that one verse immediately precedes another verse in sequence, making it the previous neighboring verse.
-
C.
neighboringVerseNext
chosen
Indicates that one verse directly follows another verse in sequence, making them adjacent neighbors in the text.
-
D.
verseBefore
Indicates that one verse occurs earlier in the ordered sequence of verses than another verse.
-
E.
featuresBackAndForthVerses
Indicates that the work contains alternating or responsive verses exchanged back and forth, typically between two or more voices or parties.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 6:19 a.m.