Triple
T12808534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantata III (Christmas Oratorio) |
E306206
|
entity |
| Predicate | hasSacredTheme |
P24743
|
FINISHED |
| Object | birth of Jesus |
—
|
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: birth of Jesus | Statement: [Cantata III (Christmas Oratorio), hasSacredTheme, birth of Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredTheme Context triple: [Cantata III (Christmas Oratorio), hasSacredTheme, birth of Jesus]
-
A.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
B.
hasSacredFunction
Indicates that something serves a religious or holy role, purpose, or duty within a sacred context.
-
C.
hasSacredSpring
Indicates that one entity possesses, contains, or is associated with a spring regarded as sacred or holy.
-
D.
hasReligiousTheme
chosen
Indicates that something (such as a work, event, or object) centrally involves or expresses religious ideas, symbols, practices, or narratives.
-
E.
sacredStatus
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e808130819080f404b3a7462c2e |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.