Triple
T11177554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunday after the Nativity |
E264449
|
entity |
| Predicate | hasProperScriptureReadings |
P5456
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Sunday after the Nativity, hasProperScriptureReadings, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProperScriptureReadings Context triple: [Sunday after the Nativity, hasProperScriptureReadings, Yes]
-
A.
hasViewOnScripture
Indicates that an entity holds a particular interpretive stance or doctrinal position regarding scripture.
-
B.
hasLiturgicalReading
chosen
Indicates that a religious service, observance, or liturgical event includes or is associated with a specific prescribed reading from scripture or other sacred text.
-
C.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
D.
scriptureRead
Indicates that an entity reads, studies, or engages with a religious or sacred text.
-
E.
hasLanguageOfScripture
Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8987e1081909b28a0bdb866beae |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.