Triple
T26565128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Örbyhus |
E666357
|
entity |
| Predicate | railwayOperatorService |
P20222
|
FINISHED |
| Object | SJ |
—
|
NE NERFINISHED |
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: SJ | Statement: [Örbyhus, railwayOperatorService, SJ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayOperatorService Context triple: [Örbyhus, railwayOperatorService, SJ]
-
A.
hasRailTransportOperator
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
B.
trainOperator
chosen
Indicates that one entity operates, manages, or runs train services for another entity or within a specific rail system.
-
C.
railwayCompany
Indicates that one entity is a railway company that owns, operates, or manages railway services or infrastructure in relation to another entity.
-
D.
railwayOwner
Indicates that one entity owns, controls, or holds proprietary rights over a railway or railway system used by another entity.
-
E.
formerRailOperator
Indicates that an entity previously operated a rail service or railway system but no longer does so.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 27, 2026, 1:54 a.m.