Triple
T1738610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North British Railway |
E37977
|
entity |
| Predicate | operatedPassengerServices |
P31751
|
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: [North British Railway, operatedPassengerServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedPassengerServices Context triple: [North British Railway, operatedPassengerServices, yes]
-
A.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
-
B.
hasPassengerOperator
Indicates that an entity (such as a vehicle or service) is operated by an organization or person responsible for carrying passengers.
-
C.
servesPassengerTrafficType
Indicates that a transportation facility or service accommodates a specified type or category of passenger traffic.
-
D.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
E.
formerPassengerService
Indicates that an entity previously provided passenger transportation services but no longer does so.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab3c2479148190badc616f8e2686d4 |
completed | March 6, 2026, 8:42 p.m. |
Created at: March 4, 2026, 7:30 p.m.