Triple
T25115542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panchayati Raj |
E629116
|
entity |
| Predicate | coversSubjects |
P103055
|
FINISHED |
| Object | 29 subjects listed in the Eleventh Schedule |
—
|
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: 29 subjects listed in the Eleventh Schedule | Statement: [Panchayati Raj, coversSubjects, 29 subjects listed in the Eleventh Schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversSubjects Context triple: [Panchayati Raj, coversSubjects, 29 subjects listed in the Eleventh Schedule]
-
A.
coveredTopics
chosen
Indicates that certain subjects or themes have been addressed or included within a discussion, document, or activity.
-
B.
titleSubjectOf
Indicates that a title (such as a book, article, or work) is about or primarily concerns a particular subject.
-
C.
subjectCategories
Indicates that an entity is associated with one or more subject-based categories or classifications.
-
D.
subjectType
Indicates the classification or category that defines what kind of entity the subject is.
-
E.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f465c66cc48190b66b14e4b9036432 |
completed | May 1, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:27 a.m.