Triple
T23803938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ScotRail East Lothian area |
E589649
|
entity |
| Predicate | farePolicyBasis |
P65069
|
FINISHED |
| Object | geographical coverage of East Lothian |
—
|
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: geographical coverage of East Lothian | Statement: [ScotRail East Lothian area, farePolicyBasis, geographical coverage of East Lothian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: farePolicyBasis Context triple: [ScotRail East Lothian area, farePolicyBasis, geographical coverage of East Lothian]
-
A.
farePolicyType
Indicates the type or category of fare policy that governs how prices, rules, or conditions are applied.
-
B.
farePolicySource
Indicates the origin or authority from which a particular fare policy is derived or defined.
-
C.
farePolicyAspect
Indicates a specific rule, condition, or feature that characterizes some aspect of a fare policy.
-
D.
fareBasis
Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
-
E.
farePolicyRelatedTo
chosen
Indicates a relationship where a fare policy is associated with, applies to, or governs a particular entity, context, or service.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c750048c8190899ff611df35b361 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:55 p.m.