Triple
T32611233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Secondary School Literacy Test |
E833655
|
entity |
| Predicate | assessmentDomain |
P18032
|
FINISHED |
| Object | reading comprehension |
—
|
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: reading comprehension | Statement: [Ontario Secondary School Literacy Test, assessmentDomain, reading comprehension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assessmentDomain Context triple: [Ontario Secondary School Literacy Test, assessmentDomain, reading comprehension]
-
A.
assessment
Indicates an evaluation or judgment made about an entity’s quality, performance, or characteristics.
-
B.
assessmentAreaDefinedBy
chosen
Indicates that the scope or domain of an assessment is specified or delimited by a particular area or boundary.
-
C.
assessmentName
Indicates the specific title or label assigned to an assessment within a system or context.
-
D.
assessmentResult
Indicates the outcome or evaluation derived from an assessment performed on an entity.
-
E.
assessmentBasis
Indicates the underlying criteria, evidence, or method used as the foundation for making an assessment or evaluation between entities.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:06 a.m.