Triple
T25441446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBSE |
E637516
|
entity |
| Predicate | administersExam |
P132315
|
FINISHED |
| Object | All India Secondary School Examination |
—
|
NE NERFINISHED |
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: All India Secondary School Examination | Statement: [CBSE, administersExam, All India Secondary School Examination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administersExam Context triple: [CBSE, administersExam, All India Secondary School Examination]
-
A.
administersTestOf
chosen
Indicates that one entity conducts or gives a test or examination to another entity.
-
B.
administeredTest
Indicates that one entity gave or conducted a test or examination to another entity.
-
C.
examSession
Indicates a relationship where a specific examination event or period is scheduled or conducted for participants.
-
D.
examProvider
Indicates that one entity is the organization or individual responsible for creating, administering, or supplying an exam to another entity.
-
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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 21, 2026, 2 p.m.