Triple
T26725385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samavayanga |
E673821
|
entity |
| Predicate | ontologyAspect |
P2312
|
FINISHED |
| Object | jīva and ajīva |
—
|
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: jīva and ajīva | Statement: [Samavayanga, ontologyAspect, jīva and ajīva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ontologyAspect Context triple: [Samavayanga, ontologyAspect, jīva and ajīva]
-
A.
ontologyStatus
Indicates the current state or condition of an entity within an ontology lifecycle (e.g., proposed, active, deprecated, or obsolete).
-
B.
ontologicalAspect
chosen
Indicates a fundamental mode or category of being that characterizes how something exists or is realized.
-
C.
conceptualAspect
Indicates that one entity represents an abstract, conceptual, or non-physical aspect, feature, or dimension of another entity.
-
D.
ontologyId
Indicates that there is an association between an entity and a specific ontology identifier that formally defines or classifies it within an ontology.
-
E.
hasOntologicalCategory
Indicates that an entity belongs to, or is classified under, a specific ontological category or type within a conceptual framework.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61809c4808190ba4c81b0eb702eee |
completed | May 2, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:42 a.m.