Triple
T2013012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwynt y Môr Wind Farm |
E43730
|
entity |
| Predicate | hasExportCables |
P1373
|
FINISHED |
| Object | subsea export cables to shore |
—
|
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: subsea export cables to shore | Statement: [Gwynt y Môr Wind Farm, hasExportCables, subsea export cables to shore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExportCables Context triple: [Gwynt y Môr Wind Farm, hasExportCables, subsea export cables to shore]
-
A.
isTypicallyWiredUsing
Indicates that one thing is commonly connected or implemented using a particular type of wiring or cabling.
-
B.
hasCouplers
Indicates that one entity is equipped with or possesses couplers that enable it to connect or link to another entity.
-
C.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
D.
cableType
chosen
Indicates the specific kind or category of cable associated with or used by an entity.
-
E.
hasNumberOfPins
Indicates that an entity is associated with a specific count of pins it possesses or uses.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b2ed6c8190ad51f0af90db2a02 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.