Triple
T23577473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labrador–Island Link |
E580299
|
entity |
| Predicate | transmissionCapacity |
P153244
|
FINISHED |
| Object | 900 MW |
—
|
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: 900 MW | Statement: [Labrador–Island Link, transmissionCapacity, 900 MW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmissionCapacity Context triple: [Labrador–Island Link, transmissionCapacity, 900 MW]
-
A.
transportCapacity
Indicates the maximum quantity of people, goods, or materials that can be transported by an entity or system within a given operation or time frame.
-
B.
trackCapacity
Indicates the maximum number of trains or amount of traffic that a specific track segment is designed to handle within a given time period.
-
C.
transmissionBand
Indicates the specific frequency range or band over which a signal, wave, or transmission is carried or allowed to pass.
-
D.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
E.
transmissionType
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd725d88190b33c8fb26603db59 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:38 p.m.