Triple
T34571754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambrosian calendar |
E887643
|
entity |
| Predicate | AdventBegins |
P65610
|
FINISHED |
| Object | two Sundays later than Roman Rite Advent |
—
|
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: two Sundays later than Roman Rite Advent | Statement: [Ambrosian calendar, AdventBegins, two Sundays later than Roman Rite Advent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AdventBegins Context triple: [Ambrosian calendar, AdventBegins, two Sundays later than Roman Rite Advent]
-
A.
LentBegins
Indicates that the period of Lent has started.
-
B.
adventLength
Indicates the duration or length of the Advent period associated with an entity or event.
-
C.
startOfLiturgicalYear
chosen
Indicates that one time or event marks the beginning of a liturgical (religious) year in a given tradition.
-
D.
holiestNightIn
Indicates that a particular night is considered the most sacred or religiously significant within a given place, context, or tradition.
-
E.
hasAdventCalendar
Indicates that one entity possesses or is associated with an advent calendar related to another entity or context.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:03 a.m.