Triple
T11379618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Église Saint-Médard |
E269558
|
entity |
| Predicate | hasMassSchedule |
P14477
|
FINISHED |
| Object | regular Sunday Mass |
—
|
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: regular Sunday Mass | Statement: [Église Saint-Médard, hasMassSchedule, regular Sunday Mass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMassSchedule Context triple: [Église Saint-Médard, hasMassSchedule, regular Sunday Mass]
-
A.
hasScheduleType
Indicates that an entity is associated with a particular kind or category of schedule (e.g., recurring, one-time, or specific scheduling pattern).
-
B.
hasPerformanceSchedule
Indicates that an entity has an associated timetable or plan specifying when its performances or shows are scheduled to occur.
-
C.
hasWorkSchedule
Indicates that an entity is assigned or follows a specific work schedule, defining when they are expected to work.
-
D.
hasAdministrationSchedule
Indicates that there is a defined plan or timetable specifying when and how an entity is to be administered or given.
-
E.
containsSchedule
chosen
Indicates that one entity includes or holds a schedule associated with another entity or activity.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e7022d508190996f9be0847c2b41 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:34 p.m.