Triple
T32611214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Secondary School Literacy Test |
E833655
|
entity |
| Predicate | hasQuestionType |
P12351
|
FINISHED |
| Object | multiple-choice questions |
—
|
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: multiple-choice questions | Statement: [Ontario Secondary School Literacy Test, hasQuestionType, multiple-choice questions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuestionType Context triple: [Ontario Secondary School Literacy Test, hasQuestionType, multiple-choice questions]
-
A.
hasAnswerType
Indicates that a question or query is associated with a specific type or category of expected answer.
-
B.
hasKeyQuestion
Indicates that one entity possesses or is associated with a primary or central question relevant to another entity.
-
C.
questionType
chosen
Indicates the specific category or kind of question that an item, query, or prompt belongs to.
-
D.
questionnaireType
Indicates the specific category or kind of questionnaire associated with an entity or interaction.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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.