Triple
T24009611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shannon hydroelectric scheme |
E594490
|
entity |
| Predicate | mainPowerStation |
P17850
|
FINISHED |
| Object | Ardnacrusha power station |
—
|
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: Ardnacrusha power station | Statement: [Shannon hydroelectric scheme, mainPowerStation, Ardnacrusha power station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPowerStation Context triple: [Shannon hydroelectric scheme, mainPowerStation, Ardnacrusha power station]
-
A.
mainCentralPower
Indicates that an entity functions as the primary central authority or dominant power within a given system or context.
-
B.
laterPowerplant
Indicates that one power plant occurs, is built, or becomes operational at a later time than another power plant.
-
C.
powerplantFor
chosen
Indicates that one entity functions as the power plant or primary energy source serving another entity.
-
D.
powerplantPower
Indicates that a power plant provides or generates a specified amount of electrical power.
-
E.
powerplant
Indicates that an entity functions as a facility or installation where energy sources are converted into usable power, typically electricity.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d46c77f88190806e6287e55c9136 |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:41 p.m.