Triple
T37496241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Board of Intermediate and Secondary Education Peshawar |
E931833
|
entity |
| Predicate | typeOfExaminations |
P52475
|
FINISHED |
| Object | annual examinations |
—
|
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: annual examinations | Statement: [Board of Intermediate and Secondary Education Peshawar, typeOfExaminations, annual examinations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfExaminations Context triple: [Board of Intermediate and Secondary Education Peshawar, typeOfExaminations, annual examinations]
-
A.
offersExaminations
Indicates that one entity provides or makes available examinations or tests to another entity.
-
B.
hasExamination
Indicates that an entity is associated with, or undergoes, a specific examination or test.
-
C.
examinedIn
Indicates that one entity is analyzed, inspected, or studied within the context, scope, or setting provided by another entity.
-
D.
typeOfInvestigation
Indicates the specific kind or category of investigation being conducted or referred to in the relationship.
-
E.
examType
chosen
Indicates the specific category or format of an exam associated with an assessment or testing event.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a036fb4650c81908df9b9ec8ed8594b |
completed | May 12, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_6a036f64dc648190a31cf944d3ea0f7d |
completed | May 12, 2026, 6:20 p.m. |
Created at: May 3, 2026, 4:17 p.m.