Triple
T10457062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Introit "Gaudete in Domino semper" |
E246574
|
entity |
| Predicate | sourceTextVerse |
P28117
|
FINISHED |
| Object | Philippians 4:4 |
—
|
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: Philippians 4:4 | Statement: [Introit "Gaudete in Domino semper", sourceTextVerse, Philippians 4:4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceTextVerse Context triple: [Introit "Gaudete in Domino semper", sourceTextVerse, Philippians 4:4]
-
A.
containsVerse
chosen
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
B.
keyVerse
Indicates that one verse is designated as the central or most thematically important verse in relation to a text, passage, or concept.
-
C.
textInESV
Indicates that a given text segment appears within the English Standard Version (ESV) of the Bible.
-
D.
textInKJV
Indicates that a given text or passage appears within the King James Version (KJV) of the Bible.
-
E.
chapterAndVerse
Indicates a relationship where a specific chapter is associated with a specific verse (or set of verses) within a structured text, such as a book or document.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe498a808190b88530f0221df4a6 |
completed | April 7, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:18 p.m.