Triple
T941969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaisheshika |
E20324
|
entity |
| Predicate | ontologyType |
P7975
|
FINISHED |
| Object | category ontology |
—
|
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: category ontology | Statement: [Vaisheshika, ontologyType, category ontology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ontologyType Context triple: [Vaisheshika, ontologyType, category ontology]
-
A.
oreType
Indicates the specific kind or classification of ore associated with an entity.
-
B.
semanticType
chosen
Indicates that something belongs to or is categorized under a particular semantic class or type based on its meaning.
-
C.
ontologicalAspect
Indicates a fundamental mode or category of being that characterizes how something exists or is realized.
-
D.
typeSpecies
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a higher-level group (such as a genus).
-
E.
termType
Indicates the classification or category of a term within a system, specifying what kind of term it is (e.g., type, role, or function) in relation to others.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3a1a4888190997adf56eb761431 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29c68f48190aecad10e351a99de |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.