Triple
T6890983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Saints |
E159043
|
entity |
| Predicate | hasDateInRomanRite |
P7861
|
FINISHED |
| Object | 1 November |
—
|
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: 1 November | Statement: [All Saints, hasDateInRomanRite, 1 November]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDateInRomanRite Context triple: [All Saints, hasDateInRomanRite, 1 November]
-
A.
dateInRomanCatholicChurch
chosen
Indicates that a specific date is recognized, observed, or used within the context of the Roman Catholic Church’s liturgical or ecclesiastical calendar.
-
B.
positionInRomanCalendar
Indicates the ordinal placement or rank that something occupies within the sequence of months or days in the Roman calendar.
-
C.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
D.
dateInAnglicanCommunion
Indicates that a given date is recognized and observed within the liturgical calendar of the Anglican Communion.
-
E.
feastDayObservedOn
Indicates that a particular feast day is celebrated or formally observed on a specified calendar date.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d92d45f08190a730b3842c95b521 |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.