Triple
T11619981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kendriya Vidyalaya Sangathan |
E275611
|
entity |
| Predicate | feeStructureType |
P25908
|
FINISHED |
| Object | subsidized |
—
|
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: subsidized | Statement: [Kendriya Vidyalaya Sangathan, feeStructureType, subsidized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feeStructureType Context triple: [Kendriya Vidyalaya Sangathan, feeStructureType, subsidized]
-
A.
feeType
Indicates the specific category or classification of a fee associated with a transaction, service, or obligation.
-
B.
fareStructure
Indicates the pricing scheme or set of rules that determine how fares are calculated and applied for a given service or trip.
-
C.
fareStructureFeature
Indicates a characteristic or condition of how fares are structured, calculated, or applied within a pricing or ticketing system.
-
D.
feePolicy
chosen
Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
-
E.
priceType
Indicates the classification or category of a price associated with an entity (e.g., list price, sale price, wholesale price).
- 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.