Triple
T17562642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercredi Saint |
E427730
|
entity |
| Predicate | calendrier |
P114346
|
FINISHED |
| Object | calendrier liturgique chrétien |
—
|
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: calendrier liturgique chrétien | Statement: [Mercredi Saint, calendrier, calendrier liturgique chrétien]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendrier Context triple: [Mercredi Saint, calendrier, calendrier liturgique chrétien]
-
A.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
B.
partOfCalendar
chosen
Indicates that one temporal element (such as an event, date, or period) belongs to, is contained within, or is scheduled as a component of a particular calendar.
-
C.
calendarFeature
Indicates that an entity provides or supports calendar-related functionality, such as scheduling, event management, or date-based organization.
-
D.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
E.
calendarFocus
Indicates that attention or interaction is currently directed toward a particular calendar or calendar-related view.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e456285c808190953a49e77366d8bd |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.