Triple
T16863231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MGB |
E409972
|
entity |
| Predicate | offersConnection |
P85512
|
FINISHED |
| Object | interchange with other Swiss railways |
—
|
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: interchange with other Swiss railways | Statement: [MGB, offersConnection, interchange with other Swiss railways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersConnection Context triple: [MGB, offersConnection, interchange with other Swiss railways]
-
A.
offersConnectionTo
chosen
Indicates that one entity provides or enables access, linkage, or connectivity to another entity.
-
B.
offersAccess
Indicates that one entity provides another entity with the ability or permission to use, enter, or interact with a resource, service, or location.
-
C.
offersEdition
Indicates that one entity provides or makes available a particular version or edition of another entity.
-
D.
offersObject
Indicates that a subject provides or makes available a specific object to another party as an offer.
-
E.
offersServiceTo
Indicates that one entity provides or makes a service available for the benefit or use of another entity.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b50488fc8190b3b646543c3ba476 |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.