Triple
T30826388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominion Cove Point LNG terminal |
E785077
|
entity |
| Predicate | connectedPipelines |
P55206
|
FINISHED |
| Object | Dominion Cove Point pipeline system |
—
|
NE NERFINISHED |
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: Dominion Cove Point pipeline system | Statement: [Dominion Cove Point LNG terminal, connectedPipelines, Dominion Cove Point pipeline system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedPipelines Context triple: [Dominion Cove Point LNG terminal, connectedPipelines, Dominion Cove Point pipeline system]
-
A.
hasPipelineConnection
chosen
Indicates that one entity is linked to another via a pipeline through which materials, fluids, or data can flow.
-
B.
operatedPipelinesIn
Indicates that an entity has operated or managed pipelines within a specified location or jurisdiction.
-
C.
hasPipes
Indicates that one entity is equipped with, contains, or is connected to one or more pipes.
-
D.
approximateNumberOfPipes
Indicates that the relationship specifies an estimated count of pipes associated with an entity.
-
E.
connectsViaCanal
Indicates that one entity is linked or joined to another by means of a canal.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: April 29, 2026, 8:44 p.m.