Triple
T35381308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travelcard Zone 8 |
E1022656
|
entity |
| Predicate | timeRestrictions |
P183080
|
FINISHED |
| Object | peak and off-peak fares apply |
—
|
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: peak and off-peak fares apply | Statement: [Travelcard Zone 8, timeRestrictions, peak and off-peak fares apply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeRestrictions Context triple: [Travelcard Zone 8, timeRestrictions, peak and off-peak fares apply]
-
A.
hoursOfOperation
Indicates the time periods during which a place or service is open and available for use.
-
B.
workHoursLimit
Indicates a constraint on the maximum number of hours an entity is allowed or scheduled to work within a specified period.
-
C.
closingTime
Indicates the specific time at which a place, service, or activity stops operating or becomes unavailable.
-
D.
restrictedOccupation
Indicates that an entity’s ability to engage in a particular occupation is limited, controlled, or prohibited under certain conditions.
-
E.
usedInBusinessHours
Indicates that something is utilized or occurs during designated business operating hours.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.