Triple
T859194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brahman |
E18561
|
entity |
| Predicate | relationshipToAtmanInAdvaita |
P2312
|
FINISHED |
| Object | Atman is identical with Brahman |
—
|
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: Atman is identical with Brahman | Statement: [Brahman, relationshipToAtmanInAdvaita, Atman is identical with Brahman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToAtmanInAdvaita Context triple: [Brahman, relationshipToAtmanInAdvaita, Atman is identical with Brahman]
-
A.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
B.
relationshipToSocrates
Indicates the specific familial, social, or conceptual connection that one entity has to Socrates.
-
C.
viewOnThingInItself
Indicates a perspective or interpretation that considers an entity as it is in itself, independent of how it appears or is experienced.
-
D.
ontologicalAspect
chosen
Indicates a fundamental mode or category of being that characterizes how something exists or is realized.
-
E.
relationToOtherCreeds
Indicates how one belief system, doctrine, or creed is positioned or related in comparison to other creeds.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac50e5ec81908ac0c4b7123b4ebb |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.