Triple
T17627492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lötschberg railway line |
E429884
|
entity |
| Predicate | baseTunnelLength |
P12895
|
FINISHED |
| Object | approximately 34.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 34.6 km | Statement: [Lötschberg railway line, baseTunnelLength, approximately 34.6 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseTunnelLength Context triple: [Lötschberg railway line, baseTunnelLength, approximately 34.6 km]
-
A.
hasTunnelLengthApprox
chosen
Indicates that an entity has a tunnel whose length is approximately a specified value.
-
B.
lengthOfTunnels
Indicates the measured extent or distance of tunnels associated with an entity.
-
C.
tunnelCircumference
Indicates the circular distance around the inner boundary of a tunnel’s cross-section.
-
D.
tunnelDiameterCharacteristic
Indicates the specified diameter-related property or measurement associated with a tunnel.
-
E.
partOfTunnel
Indicates that one entity forms a physical segment or component within the structure or extent of a tunnel.
- 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.