Triple
T17627491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lötschberg railway line |
E429884
|
entity |
| Predicate | summitTunnelLength |
P114992
|
FINISHED |
| Object | approximately 14.6 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: approximately 14.6 km | Statement: [Lötschberg railway line, summitTunnelLength, approximately 14.6 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitTunnelLength Context triple: [Lötschberg railway line, summitTunnelLength, approximately 14.6 km]
-
A.
hasSummitTunnel
Indicates that a summit or peak contains or is traversed by a tunnel.
-
B.
lengthOfTunnels
chosen
Indicates the measured extent or distance of tunnels associated with an entity.
-
C.
numberOfMajorTunnels
Indicates the count of primary or significant tunnels associated with an entity.
-
D.
undergroundCavernLength
Indicates the measured linear extent or distance from one end to the other of an underground cavern.
-
E.
summitDepth
Indicates the vertical distance from a summit’s highest point down to a specified reference level, such as a base or surrounding terrain.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dbe3a308190a818d04f1a9b15f7 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.