Triple
T11619983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kendriya Vidyalaya Sangathan |
E275611
|
entity |
| Predicate | schoolManagement |
P84912
|
FINISHED |
| Object | centralized |
—
|
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: centralized | Statement: [Kendriya Vidyalaya Sangathan, schoolManagement, centralized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schoolManagement Context triple: [Kendriya Vidyalaya Sangathan, schoolManagement, centralized]
-
A.
schoolBoardSystem
chosen
Indicates a governance or administrative relationship in which a school board oversees, manages, or makes decisions for a school system or district.
-
B.
schoolBoard
Indicates that an entity serves as or is governed by a school board responsible for overseeing educational policies and administration.
-
C.
schoolRoll
Indicates the official list or record of students enrolled in a particular school or class.
-
D.
school
Indicates that an entity attends, is enrolled in, or is institutionally associated as a student with a particular school.
-
E.
schoolSector
Indicates the educational sector or category (such as public, private, or charter) to which a school belongs.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a1206f1c81908d92024ef71958c0 |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.