Triple
T11717547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glossop line |
E278539
|
entity |
| Predicate | hasPeakServices |
P27955
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Glossop line, hasPeakServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeakServices Context triple: [Glossop line, hasPeakServices, yes]
-
A.
hasPeakDirectionService
Indicates that a transportation service operates primarily or exclusively in a specified direction during peak travel periods.
-
B.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
C.
hasPeakHourService
chosen
Indicates that a service operates or is available during designated peak or high-demand hours.
-
D.
hasPeakAssociated
Indicates that one entity is linked or related to a specific peak (such as a summit or maximum point) associated with it.
-
E.
hasPeakHourFunction
Indicates that something performs a specific role or behavior during peak hours of activity or usage.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c10d988190842acd824135cf15 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.