Triple
T21208729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farncombe Church of England Infant School |
E522659
|
entity |
| Predicate | hasOfstedRegistered |
P143556
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Farncombe Church of England Infant School, hasOfstedRegistered, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfstedRegistered Context triple: [Farncombe Church of England Infant School, hasOfstedRegistered, true]
-
A.
hasOfstedStatus
Indicates that an educational institution has a particular inspection or regulatory status as determined by Ofsted.
-
B.
hasOfstedInspection
Indicates that an entity has undergone an inspection carried out by Ofsted.
-
C.
hasOfstedEquivalent
Indicates that an entity has a corresponding or comparable organization, standard, or evaluation body equivalent to Ofsted in another context or jurisdiction.
-
D.
hasOfstedInspectionYear
Indicates the year in which an entity underwent an Ofsted inspection.
-
E.
hasEducationAuthority
Indicates that one entity holds official power or responsibility to make decisions or govern matters related to another entity’s education.
- F. None of above. chosen
Provenance (4 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73436eb4c819082e05caf1ba52672 |
completed | April 21, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5fa92a2448190896c022dd27511ad |
completed | April 20, 2026, 10:06 a.m. |
Created at: April 16, 2026, 3:25 p.m.