Triple
T6449622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ardnacrusha power station |
E139829
|
entity |
| Predicate | maximumElectricPower |
P18504
|
FINISHED |
| Object | 86 megawatt |
—
|
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: 86 megawatt | Statement: [Ardnacrusha power station, maximumElectricPower, 86 megawatt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumElectricPower Context triple: [Ardnacrusha power station, maximumElectricPower, 86 megawatt]
-
A.
maximumPowerDuringOperation
chosen
Indicates the highest level of power that occurs while the system or component is operating.
-
B.
maximumPowerAtPSE
Indicates the highest level of power that can be delivered or drawn at the Power Sourcing Equipment (PSE) in the relationship.
-
C.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
-
D.
maxVoltage
Indicates the maximum electrical potential (voltage) that an entity can safely or normally handle, provide, or operate at.
-
E.
designPowerOutput
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
- 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_69c008b301948190a35854e5284dc822 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069b2c7bc81908c683ec22cad9628 |
completed | March 22, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:47 p.m.