Triple
T10145605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire and Rescue Services Act 2004 |
E231697
|
entity |
| Predicate | providesPower |
P56956
|
FINISHED |
| Object | power to respond to other emergencies |
—
|
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: power to respond to other emergencies | Statement: [Fire and Rescue Services Act 2004, providesPower, power to respond to other emergencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesPower Context triple: [Fire and Rescue Services Act 2004, providesPower, power to respond to other emergencies]
-
A.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
B.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
C.
enablingPowerFor
chosen
Indicates that one entity provides the capability or authority that allows another entity to perform a specific function, action, or role.
-
D.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
-
E.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
- 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdeb2a373081908615f7b2314e7f90 |
completed | April 2, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:07 p.m.