Triple
T32058805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Branch Tunnel |
E818690
|
entity |
| Predicate | conduitType |
P173162
|
FINISHED |
| Object | pressure tunnel |
—
|
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: pressure tunnel | Statement: [West Branch Tunnel, conduitType, pressure tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conduitType Context triple: [West Branch Tunnel, conduitType, pressure tunnel]
-
A.
primaryConduitType
Indicates the main type or category of conduit used as the primary pathway for a connection or flow between entities.
-
B.
pipeType
Indicates the specific kind or category of pipe associated with or used in relation to an entity.
-
C.
inletType
Indicates the specific kind or category of inlet through which something (such as a fluid, signal, or material) enters a system or component.
-
D.
enclosedInConduits
Indicates that one entity is physically contained or routed within conduit structures provided by another entity.
-
E.
circuitType
Indicates the specific kind or category of electrical circuit associated with an entity.
- F. None of above. chosen
Provenance (4 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4f1be488190823ce96ea65f1c80 |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b267b90c8190807208cadce5ae8d |
completed | May 3, 2026, 2:26 a.m. |
Created at: May 1, 2026, 12:21 a.m.