Triple
T25237769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Education Act 1944 |
E632383
|
entity |
| Predicate | establishedDutyOf |
P142368
|
FINISHED |
| Object | local education 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 education authorities | Statement: [Education Act 1944, establishedDutyOf, local education authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedDutyOf Context triple: [Education Act 1944, establishedDutyOf, local education authorities]
-
A.
dutyRecognized
Indicates that an obligation or responsibility has been acknowledged or accepted by the relevant party.
-
B.
statutoryDuty
chosen
Indicates that an entity is legally obligated by statute to perform, refrain from, or ensure a specific action or condition.
-
C.
expectedDuty
Indicates that one entity is obligated or anticipated to perform a particular duty or responsibility toward another entity or within a given context.
-
D.
stressesDutyTo
Indicates that one entity emphasizes or underscores the responsibility, obligation, or duty of another entity.
-
E.
createsDuty
Indicates that one entity brings about an obligation or responsibility for another entity to perform or uphold something.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 1:07 p.m.