Triple
T17156354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estyn |
E416351
|
entity |
| Predicate | usesInspectionCycle |
P42603
|
FINISHED |
| Object | regular scheduled inspections |
—
|
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: regular scheduled inspections | Statement: [Estyn, usesInspectionCycle, regular scheduled inspections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInspectionCycle Context triple: [Estyn, usesInspectionCycle, regular scheduled inspections]
-
A.
isInspected
Indicates that an entity is examined or checked by another entity to assess its condition, quality, or compliance.
-
B.
includedInCycle
chosen
Indicates that an entity participates in and is part of a closed loop or recurring sequence within a system or structure.
-
C.
isCyclic
Indicates that a structure, process, or sequence forms a closed loop in which elements or states repeat in a cycle.
-
D.
hasCycleAccess
Indicates that an entity is permitted to use or access a bicycle or cycling-related resource.
-
E.
usesRepetition
Indicates that one entity employs repeated elements, actions, or patterns as a deliberate feature or technique in relation to another entity or context.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f40b402881908b8c01d7b957d0d2 |
completed | April 18, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.