Triple
T11619985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kendriya Vidyalaya Sangathan |
E275611
|
entity |
| Predicate | hasCommonSyllabus |
P100627
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kendriya Vidyalaya Sangathan, hasCommonSyllabus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonSyllabus Context triple: [Kendriya Vidyalaya Sangathan, hasCommonSyllabus, yes]
-
A.
commonlyTaughtWith
Indicates that two subjects or concepts are frequently taught together within the same course, lesson, or curriculum context.
-
B.
hasCurricularStructure
Indicates that an educational program or course is organized according to a defined curricular framework or structure.
-
C.
hasCoursePattern
Indicates that an entity follows, is associated with, or is defined by a particular course structure or pattern.
-
D.
hasCurriculumScope
Indicates that a curriculum or educational program applies to, or is defined within, a particular scope or context (such as grade level, subject area, or institution).
-
E.
hasGradeSystem
Indicates that one entity uses, follows, or is governed by a particular grading or evaluation system defined by another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.