Triple
T25492389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Education (Schools) Act 1992 |
E638868
|
entity |
| Predicate | introducedRequirementFor |
P39303
|
FINISHED |
| Object | inspection reports to be made public |
—
|
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: inspection reports to be made public | Statement: [Education (Schools) Act 1992, introducedRequirementFor, inspection reports to be made public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedRequirementFor Context triple: [Education (Schools) Act 1992, introducedRequirementFor, inspection reports to be made public]
-
A.
establishedRequirement
chosen
Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
-
B.
expandedRequirement
Indicates that one requirement elaborates, refines, or adds detail to another requirement.
-
C.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
D.
relatedRequirement
Indicates that one requirement has a defined relationship or dependency with another requirement.
-
E.
designedToMeetRequirement
Indicates that something has been intentionally created or configured in order to satisfy a specified requirement.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 21, 2026, 2:39 p.m.