Triple
T2824381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epistle to the Colossians |
E54885
|
entity |
| Predicate | containsChristHymn |
P21130
|
FINISHED |
| Object | Colossians 1:15-20 |
—
|
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:15-20 | Statement: [Epistle to the Colossians, containsChristHymn, Colossians 1:15-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsChristHymn Context triple: [Epistle to the Colossians, containsChristHymn, Colossians 1:15-20]
-
A.
hasChristologicalUse
Indicates that something is used or interpreted in a way that relates specifically to the person, nature, or work of Christ within Christian theology.
-
B.
importantHymn
chosen
Indicates that a hymn holds significant importance or prominence within a particular religious, cultural, or musical context.
-
C.
emphasizesAttributeOfChrist
Indicates that something highlights, underscores, or draws special attention to a particular attribute or quality of Christ.
-
D.
isChristmasSong
Indicates that a song is recognized as a Christmas-themed song, typically associated with the Christmas holiday season.
-
E.
hasChoir
Indicates that an entity possesses, maintains, or is associated with a choir.
- 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.