Triple
T38134060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tube Stock |
E952298
|
entity |
| Predicate | operatesInTunnelType |
P139266
|
FINISHED |
| Object | deep-level bored 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: deep-level bored tunnels | Statement: [Tube Stock, operatesInTunnelType, deep-level bored tunnels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInTunnelType Context triple: [Tube Stock, operatesInTunnelType, deep-level bored tunnels]
-
A.
tunnelType
Indicates the specific kind or classification of a tunnel associated with an entity.
-
B.
tunnelOperationMode
Indicates the specific operational state or mode in which a tunnel system or tunnel-related process is currently functioning.
-
C.
canOperateInTunnels
chosen
Indicates that the subject has the capability or is permitted to function or be used within tunnel environments.
-
D.
tunnelsProtocol
Indicates that one communication protocol is encapsulated and transmitted within another protocol, creating a tunnel through the outer protocol’s channel.
-
E.
usesTunnel
Indicates that one entity makes use of a tunnel as a passage or route to reach or connect to another entity.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0349d158b881908bfbdb501ea565ee |
completed | May 12, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_6a034750e3d48190a88ee3604a36b46d |
completed | May 12, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:21 p.m.