Triple
T34079307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norfolk Southern Pittsburgh Line |
E873988
|
entity |
| Predicate | hasTunnelStructures |
P61738
|
FINISHED |
| Object | multiple mountain tunnels |
—
|
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: multiple mountain tunnels | Statement: [Norfolk Southern Pittsburgh Line, hasTunnelStructures, multiple mountain tunnels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTunnelStructures Context triple: [Norfolk Southern Pittsburgh Line, hasTunnelStructures, multiple mountain tunnels]
-
A.
hasRailwayTunnel
chosen
Indicates that one entity contains, includes, or is connected by a railway tunnel associated with the other entity.
-
B.
hasSummitTunnel
Indicates that a summit or peak contains or is traversed by a tunnel.
-
C.
hasMilitaryTunnels
Indicates that one location possesses or contains underground tunnels used for military purposes in relation to another entity.
-
D.
hasBridgeAndTunnelStructures
Indicates that there exist both bridge and tunnel structures associated with or connecting the related entities.
-
E.
hasRockTunnel
Indicates that one entity possesses, contains, or provides access to a tunnel that passes through rock.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:52 a.m.