Triple
T873373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emergency Powers (Defence) Act 1939 |
E18862
|
entity |
| Predicate | enablingPower |
P7884
|
FINISHED |
| Object | power to make Defence Regulations |
—
|
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 make Defence Regulations | Statement: [Emergency Powers (Defence) Act 1939, enablingPower, power to make Defence Regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablingPower Context triple: [Emergency Powers (Defence) Act 1939, enablingPower, power to make Defence Regulations]
-
A.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
B.
grantedPower
chosen
Indicates that one entity has conferred authority, control, or a specific capability to another entity.
-
C.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
D.
definesPoweringMode
Indicates that one entity specifies or determines the operating or powering mode used by another entity.
-
E.
supportsPowerLevel
Indicates that one entity is capable of providing or sustaining the required power level for another entity or operation.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac97d0f88190b67fcb7fc058e4b9 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8b9b5c81909ac71904f8b8b5cd |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.