Triple
T5546971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edinburgh–Perth commuter services |
E145431
|
entity |
| Predicate | hasRegularServicePattern |
P65303
|
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: [Edinburgh–Perth commuter services, hasRegularServicePattern, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegularServicePattern Context triple: [Edinburgh–Perth commuter services, hasRegularServicePattern, true]
-
A.
hasServicePatternRole
Indicates that an entity participates in a service pattern with a specific functional role or responsibility within that pattern.
-
B.
hasServicePatternNote
Indicates that a service pattern (such as a schedule or routing pattern) is associated with a specific explanatory note or annotation.
-
C.
hasServicePatternChange
Indicates that there is a modification in the usual or scheduled pattern of a service’s operation.
-
D.
hasRegularity
Indicates that one entity exhibits a consistent, recurring pattern or uniform behavior with respect to another entity or over time.
-
E.
includesServicePattern
Indicates that one entity contains or incorporates a particular service pattern as part of its structure or configuration.
- 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_69c008fb879c81909f5bfa56fadc1d46 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fdec3588190b0af7d2ca8e8ee9b |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:35 p.m.