Triple
T8376342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electricity (Supply) Act 1926 |
E197584
|
entity |
| Predicate | aimedToIncrease |
P7907
|
FINISHED |
| Object | reliability of electricity supply |
—
|
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: reliability of electricity supply | Statement: [Electricity (Supply) Act 1926, aimedToIncrease, reliability of electricity supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimedToIncrease Context triple: [Electricity (Supply) Act 1926, aimedToIncrease, reliability of electricity supply]
-
A.
aimedToFacilitate
Indicates an action or arrangement that was intentionally designed to make another process, event, or outcome easier or more likely to occur.
-
B.
increases
chosen
Indicates that one entity causes another entity’s value, level, or intensity to become larger or higher.
-
C.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
D.
aimedToEstablish
Indicates an intention or effort directed toward creating, founding, or setting up something.
-
E.
aimedToLimit
Indicates an action or policy that was intentionally directed toward restricting, reducing, or constraining something.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80bf6b8081909b98762b1f900bef |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:01 p.m.