Triple
T4205293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ScotRail Fife zone |
E86168
|
entity |
| Predicate | appliesToServiceType |
P53961
|
FINISHED |
| Object | passenger rail services |
—
|
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: passenger rail services | Statement: [ScotRail Fife zone, appliesToServiceType, passenger rail services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToServiceType Context triple: [ScotRail Fife zone, appliesToServiceType, passenger rail services]
-
A.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
appliesToProductType
Indicates that something (such as a rule, offer, or condition) is relevant or applicable specifically to a certain type or category of product.
-
C.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
D.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
-
E.
appliesToPropertyType
Indicates that something (such as a rule, constraint, or operation) is relevant to or valid for a specific type of property.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0382eafc8190946bf45bf28095dd |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af0196716c81908b99193690630a29 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af021828208190beb6d1af367b5a65 |
completed | March 9, 2026, 5:23 p.m. |
Created at: March 9, 2026, 3:49 p.m.