Triple
T27763872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grüsch |
E701547
|
entity |
| Predicate | operatorOfRailServices |
P20222
|
FINISHED |
| Object | Rhaetian Railway |
—
|
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: Rhaetian Railway | Statement: [Grüsch, operatorOfRailServices, Rhaetian Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorOfRailServices Context triple: [Grüsch, operatorOfRailServices, Rhaetian Railway]
-
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.
railOperatorBeneficiary
Indicates that a rail operator is the beneficiary of some benefit, service, right, or outcome provided by another party or arrangement.
-
D.
operatesRegionalRailServices
Indicates that an entity manages and runs passenger rail transport services within a specific region or set of regions.
-
E.
railServiceType
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: April 27, 2026, 4:29 p.m.