Triple
T10145600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire and Rescue Services Act 2004 |
E231697
|
entity |
| Predicate | coreDuty |
P56094
|
FINISHED |
| Object | 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: firefighting | Statement: [Fire and Rescue Services Act 2004, coreDuty, firefighting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreDuty Context triple: [Fire and Rescue Services Act 2004, coreDuty, firefighting]
-
A.
performsDuty
Indicates that one entity carries out or fulfills a responsibility, task, or obligation on behalf of or in relation to another entity.
-
B.
hasPrimaryDuty
chosen
Indicates that one entity holds the main or most important responsibility or obligation toward another entity or within a specified context.
-
C.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
D.
createsDuty
Indicates that one entity brings about an obligation or responsibility for another entity to perform or uphold something.
-
E.
coreHolding
Indicates a primary or central ownership relationship where one entity holds a significant, foundational stake or position in another.
- 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.