Triple
T28755455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schynige Platte Railway |
E731657
|
entity |
| Predicate | rackRailwayLength |
P77732
|
FINISHED |
| Object | 7.26 km |
—
|
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: 7.26 km | Statement: [Schynige Platte Railway, rackRailwayLength, 7.26 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rackRailwayLength Context triple: [Schynige Platte Railway, rackRailwayLength, 7.26 km]
-
A.
railwayLineLength
chosen
Indicates the total measured length of a railway line.
-
B.
railwayNetworkLength
Indicates the total measured length of all railway tracks within a specified railway network.
-
C.
rollingStockLength
Indicates the length measurement of a piece of rolling stock in a rail or transit system.
-
D.
railTrackLengthPerArm
Indicates the length of rail track associated with each individual arm in the system.
-
E.
hasRackRailway
Indicates that one entity possesses or includes a rack railway system connecting locations or operating within its area.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657fb2bc48190882778ab59298445 |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f651ada6048190a7b4a6981565dc3a |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 6:09 a.m.