Triple
T30470010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thrill Hill East |
E775264
|
entity |
| Predicate | hasRecordingScheduleFlexibility |
P202395
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Thrill Hill East, hasRecordingScheduleFlexibility, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordingScheduleFlexibility Context triple: [Thrill Hill East, hasRecordingScheduleFlexibility, true]
-
A.
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.
-
B.
availabilityPattern
Indicates a recurring schedule or pattern that defines when something is available or unavailable over time.
-
C.
flexibleSchedulingNetwork
Indicates a relationship where entities are connected through the ability to arrange or adjust schedules flexibly to accommodate varying times, needs, or constraints.
-
D.
usesScheduleFormat
Indicates that one entity adopts or follows the schedule structure, pattern, or formatting defined by another entity.
-
E.
fareFlexibility
Indicates how easily a fare can be changed, canceled, or refunded, and under what conditions or penalties.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0079e152648190a9da2add94fc1831 |
completed | May 10, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a0078f77f9c8190af357a6016a2bd53 |
completed | May 10, 2026, 12:24 p.m. |
| PDg | Predicate description generation | batch_6a0079e0a9688190a420759fafd47807 |
completed | May 10, 2026, 12:28 p.m. |
Created at: April 29, 2026, 8:11 p.m.