Triple
T26333322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evangelische Stadtkirche Dillenburg |
E662450
|
entity |
| Predicate | hasServiceSchedule |
P60792
|
FINISHED |
| Object | regular Sunday services |
—
|
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 services | Statement: [Evangelische Stadtkirche Dillenburg, hasServiceSchedule, regular Sunday services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceSchedule Context triple: [Evangelische Stadtkirche Dillenburg, hasServiceSchedule, regular Sunday services]
-
A.
hasAdministrationSchedule
Indicates that there is a defined plan or timetable specifying when and how an entity is to be administered or given.
-
B.
hasMeetingSchedule
chosen
Indicates that an entity has an associated plan or timetable specifying when meetings are to occur.
-
C.
hasWorkSchedule
Indicates that an entity is assigned or follows a specific work schedule, defining when they are expected to work.
-
D.
hasAppointmentSystem
Indicates that an entity uses or provides a structured system for scheduling, managing, and tracking appointments.
-
E.
canSchedule
Indicates that one entity has the ability or permission to arrange or set a time for an event, task, or activity involving another entity.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 26, 2026, 10:34 p.m.