Triple
T32962747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Ninian's High School |
E843282
|
entity |
| Predicate | hasInspectionRating |
P59739
|
FINISHED |
| Object | positive reports for attainment |
—
|
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: positive reports for attainment | Statement: [St Ninian's High School, hasInspectionRating, positive reports for attainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInspectionRating Context triple: [St Ninian's High School, hasInspectionRating, positive reports for attainment]
-
A.
hasRatingType
Indicates that an entity is associated with a specific kind or category of rating it receives or uses.
-
B.
hasCurrentRating
Indicates that an entity is associated with its present or most up-to-date rating value.
-
C.
hasRatingLevel
chosen
Indicates that an entity is associated with a particular rating level or score category.
-
D.
hasEvaluation
Indicates that an entity has been assessed or judged according to some criteria, linking it to the corresponding evaluation result or record.
-
E.
isInspected
Indicates that an entity is examined or checked by another entity to assess its condition, quality, or compliance.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
Created at: May 1, 2026, 1:21 a.m.