Triple
T33003318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Services Act 1947 |
E844429
|
entity |
| Predicate | createdDutyFor |
P75527
|
FINISHED |
| Object | local fire authorities |
—
|
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: local fire authorities | Statement: [Fire Services Act 1947, createdDutyFor, local fire authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdDutyFor Context triple: [Fire Services Act 1947, createdDutyFor, local fire authorities]
-
A.
createsDuty
chosen
Indicates that one entity brings about an obligation or responsibility for another entity to perform or uphold something.
-
B.
performsDuty
Indicates that one entity carries out or fulfills a responsibility, task, or obligation on behalf of or in relation to another entity.
-
C.
laterDuty
Indicates that one entity has a duty, obligation, or responsibility that occurs after or subsequent to another referenced duty or time.
-
D.
expectedDuty
Indicates that one entity is obligated or anticipated to perform a particular duty or responsibility toward another entity or within a given context.
-
E.
createdWork
Indicates that an agent is responsible for bringing a work (such as a creative, intellectual, or produced artifact) into existence.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 1, 2026, 1:23 a.m.