Triple
T34747378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern line extension to Battersea |
E1001673
|
entity |
| Predicate | usesTunnels |
P155518
|
FINISHED |
| Object | twin-bore running 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: twin-bore running tunnels | Statement: [Northern line extension to Battersea, usesTunnels, twin-bore running tunnels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTunnels Context triple: [Northern line extension to Battersea, usesTunnels, twin-bore running tunnels]
-
A.
usesTunnel
Indicates that one entity makes use of a tunnel as a passage or route to reach or connect to another entity.
-
B.
tunnelUse
chosen
Indicates that one entity makes use of or passes through a tunnel associated with another entity.
-
C.
usesTunnelOrBridge
Indicates that one entity travels or passes between locations by means of a tunnel or a bridge.
-
D.
hasTunnel
Indicates that one entity possesses, contains, or is connected by a tunnel to another entity.
-
E.
canOperateInTunnels
Indicates that the subject has the capability or is permitted to function or be used within tunnel environments.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 3:59 p.m.