Triple
T33003319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Services Act 1947 |
E844429
|
entity |
| Predicate | imposedDuty |
P7925
|
FINISHED |
| Object | to make provision for firefighting |
—
|
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: to make provision for firefighting | Statement: [Fire Services Act 1947, imposedDuty, to make provision for firefighting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imposedDuty Context triple: [Fire Services Act 1947, imposedDuty, to make provision for firefighting]
-
A.
imposesDutyOnIndividuals
Indicates that an authority or rule places an obligation or responsibility on individuals to perform or refrain from certain actions.
-
B.
imposes
chosen
Indicates that one entity enforces, applies, or places a rule, condition, burden, or obligation upon another entity.
-
C.
dutyLoad
Indicates the amount or extent of responsibility, work, or obligations assigned to an entity.
-
D.
imposedOn
Indicates that one party enforces, applies, or places a requirement, burden, or constraint onto another party or entity.
-
E.
imposedDominanceOf
Indicates that one entity has forcibly asserted control, authority, or superiority over another, typically without the latter’s consent.
- 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_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:23 a.m.