Triple
T1162900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gigha |
E24532
|
entity |
| Predicate | hasGridConnection |
P25653
|
FINISHED |
| Object | subsea cable to mainland |
—
|
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 cable to mainland | Statement: [Gigha, hasGridConnection, subsea cable to mainland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGridConnection Context triple: [Gigha, hasGridConnection, subsea cable to mainland]
-
A.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
B.
usesElectricalPlug
Indicates that one entity operates by being connected to another entity via an electrical plug.
-
C.
hasEnergyManagement
Indicates that an entity possesses or is associated with a system, capability, or function for monitoring, controlling, or optimizing energy use.
-
D.
typeOfElectricity
Indicates that one entity specifies the particular kind or category of electricity associated with another entity.
-
E.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of another 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcb2bb84819088bd94e91c10fb0c |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bc49693c8190978ec63a5171d342 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:45 p.m.