Triple
T17601515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mosspark |
E428711
|
entity |
| Predicate | typicalFrequencyWeekday |
P90998
|
FINISHED |
| Object | half-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: half-hourly service | Statement: [Mosspark, typicalFrequencyWeekday, half-hourly service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFrequencyWeekday Context triple: [Mosspark, typicalFrequencyWeekday, half-hourly service]
-
A.
typicalFrequencyWeekdayDaytime
chosen
Indicates the usual or most common frequency with which something occurs during daytime hours on weekdays.
-
B.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
C.
typicalEventDay
Indicates the day on which an event is normally or most commonly held or occurs.
-
D.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
E.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
- 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_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_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.