Triple
T17601517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mosspark |
E428711
|
entity |
| Predicate | typicalFrequencySunday |
P128182
|
FINISHED |
| Object | hourly service |
—
|
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: hourly service | Statement: [Mosspark, typicalFrequencySunday, hourly service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFrequencySunday Context triple: [Mosspark, typicalFrequencySunday, hourly service]
-
A.
typicalFrequencyWeekdayDaytime
Indicates the usual or most common frequency with which something occurs during daytime hours on weekdays.
-
B.
celebratedOnSundayIn
Indicates that an event, ritual, or observance is held or carried out on a Sunday within a specified place or time period.
-
C.
hasWeeklyHolyDay
Indicates that an entity observes or is associated with a recurring holy or sacred day that occurs weekly.
-
D.
sundayLawDate
Indicates the date on which a specific Sunday law is enacted, comes into effect, or is scheduled to be observed.
-
E.
typicalFrequencyUnit
Indicates the unit of measurement typically used to express the frequency of an event, action, or occurrence.
- F. None of above. chosen
Provenance (4 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c48dfc08190ba360e6082cffa87 |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b500c924819087c7107f86970675 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:51 a.m.