Triple
T9117505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantique de Noël |
E218758
|
entity |
| Predicate | EnglishTextIncipit |
P67696
|
FINISHED |
| Object | O holy night, the stars are brightly shining |
—
|
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: O holy night, the stars are brightly shining | Statement: [Cantique de Noël, EnglishTextIncipit, O holy night, the stars are brightly shining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EnglishTextIncipit Context triple: [Cantique de Noël, EnglishTextIncipit, O holy night, the stars are brightly shining]
-
A.
hasEnglishIncipit
chosen
Indicates that an entity has an opening phrase or initial text (incipit) expressed in English.
-
B.
openingVerseTranslation
Indicates the specific translated rendering of the opening verse of a text or work.
-
C.
textInNIV
Indicates that a given text or passage appears in, or is taken from, the New International Version (NIV) of the Bible.
-
D.
textOpeningTranslation
Indicates that a text serves as a translation of the opening section of another text.
-
E.
textInESV
Indicates that a given text segment appears within the English Standard Version (ESV) of the Bible.
- 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_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a5e2ac8190b602ef0c77deb2fa |
completed | April 1, 2026, 5:09 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.