Triple
T2824379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epistle to the Colossians |
E54885
|
entity |
| Predicate | openingVerseReference |
P28117
|
FINISHED |
| Object | Colossians 1:1 |
—
|
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: Colossians 1:1 | Statement: [Epistle to the Colossians, openingVerseReference, Colossians 1:1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingVerseReference Context triple: [Epistle to the Colossians, openingVerseReference, Colossians 1:1]
-
A.
openingVerseType
Indicates the specific kind or category of an opening verse used at the beginning of a text, performance, or composition.
-
B.
openingVerseTheme
Indicates the primary idea or motif expressed in the opening verse of a text, song, or poem.
-
C.
keyVerse
Indicates that one verse is designated as the central or most thematically important verse in relation to a text, passage, or concept.
-
D.
containsVerse
chosen
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
E.
firstVerseText
Indicates the textual content that appears in the first verse of something, such as a song, poem, or hymn.
- 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abdf15b7288190a03d1193cc0544a6 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd08f2f481908c3da8a9c7a00552 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.