Triple
T37195185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Hydroelectric Power Corporation |
E921570
|
entity |
| Predicate | PSUCategory |
P187515
|
FINISHED |
| Object | Mini Ratna |
—
|
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: Mini Ratna | Statement: [National Hydroelectric Power Corporation, PSUCategory, Mini Ratna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PSUCategory Context triple: [National Hydroelectric Power Corporation, PSUCategory, Mini Ratna]
-
A.
UCICategory
Indicates that an entity is classified under a specific UCICategory, representing its assigned category or type within a defined classification scheme.
-
B.
coreCategory
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
-
C.
campusCategory
Indicates the classification or type assigned to a campus within a broader organizational or geographic system.
-
D.
unitCategory
Indicates the classification or type of unit that an entity belongs to within a defined system or context.
-
E.
subjectCategories
Indicates that an entity is associated with one or more subject-based categories or classifications.
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb55dc36d08190a0634fa680e13114 |
completed | May 6, 2026, 2:53 p.m. |
Created at: May 3, 2026, 4:15 p.m.