Triple
T23526778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaisesika Sutra |
E576454
|
entity |
| Predicate | detailsConcept |
P153106
|
FINISHED |
| Object | substance (dravya) |
—
|
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: substance (dravya) | Statement: [Vaisesika Sutra, detailsConcept, substance (dravya)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detailsConcept Context triple: [Vaisesika Sutra, detailsConcept, substance (dravya)]
-
A.
featuredConcept
Indicates that one concept is highlighted or given special prominence relative to others in a particular context.
-
B.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
C.
scientificConcept
Indicates that one entity is a scientific idea, principle, or theory that defines, explains, or characterizes the other entity.
-
D.
conceptualAspect
Indicates that one entity represents an abstract, conceptual, or non-physical aspect, feature, or dimension of another entity.
-
E.
primaryConcept
Indicates that one concept is the main or central idea in relation to another concept or context.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac74be1881909161b94aa611188a |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:09 p.m.