Triple
T11967350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Interconnection |
E284822
|
entity |
| Predicate | interconnectedVia |
P845
|
FINISHED |
| Object | high-voltage direct current ties |
—
|
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: high-voltage direct current ties | Statement: [Western Interconnection, interconnectedVia, high-voltage direct current ties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interconnectedVia Context triple: [Western Interconnection, interconnectedVia, high-voltage direct current ties]
-
A.
interconnectionType
Indicates the specific kind or nature of relationship that links two or more entities together.
-
B.
connectsTo
chosen
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
C.
connectedByStraitTo
Indicates that one entity is geographically linked to another by a narrow body of water known as a strait.
-
D.
connectsViaCanal
Indicates that one entity is linked or joined to another by means of a canal.
-
E.
hasInterchangesWith
Indicates that two transportation routes, lines, or services share one or more points where passengers can transfer between them.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037adf5881908abe1a4e64a71f20 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:46 p.m.