Triple
T11847871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specialized High Schools Admissions Test |
E281826
|
entity |
| Predicate | subjectTested |
P66416
|
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: [Specialized High Schools Admissions Test, subjectTested, reading comprehension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectTested Context triple: [Specialized High Schools Admissions Test, subjectTested, reading comprehension]
-
A.
subjectTestsStatus
Indicates that a subject performs a test to determine or verify the status or condition of another entity.
-
B.
writtenExamSubjectsInclude
chosen
Indicates that the set of subjects specified is included among the subjects covered by a particular written exam.
-
C.
examType
Indicates the specific category or format of an exam associated with an assessment or testing event.
-
D.
subjectType
Indicates the classification or category that defines what kind of entity the subject is.
-
E.
examSystem
Indicates a relationship where an entity functions as or belongs to an examination system, such as a framework or platform for creating, administering, or managing exams.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65c72088190b8de9550c455b788 |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.