Triple
T15317717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roshen Fountain in Vinnytsia |
E366204
|
entity |
| Predicate | hasDailySchedule |
P71495
|
FINISHED |
| Object | evening shows |
—
|
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: evening shows | Statement: [Roshen Fountain in Vinnytsia, hasDailySchedule, evening shows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDailySchedule Context triple: [Roshen Fountain in Vinnytsia, hasDailySchedule, evening shows]
-
A.
hasDailyEvent
chosen
Indicates that an entity is associated with an event that occurs every day.
-
B.
hasDailyService
Indicates that a service or operation occurs every day on a regular, scheduled basis.
-
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.
hasDailyUse
Indicates that something is used or occurs on a daily, regular basis.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd1d384819098f38402a8740d91 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.