Triple
T17952543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turiya |
E448866
|
entity |
| Predicate | isEquatedWith |
P107996
|
FINISHED |
| Object | liberation (moksha) |
—
|
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: liberation (moksha) | Statement: [Turiya, isEquatedWith, liberation (moksha)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEquatedWith Context triple: [Turiya, isEquatedWith, liberation (moksha)]
-
A.
equivalentTo
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
B.
isEquiconsistentWith
Indicates that two formal theories or systems have the same consistency strength, such that if one is consistent then the other is also consistent, and if one is inconsistent then so is the other.
-
C.
hasEquivalent
Indicates that two entities are considered equal in value, meaning, or function within a given context.
-
D.
isEquityOf
Indicates that one entity represents an ownership interest (equity stake) in another entity.
-
E.
oftenEquatedWith
chosen
Indicates that one entity is frequently regarded, interpreted, or treated as being the same as or equivalent to another entity, though not necessarily strictly identical.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afad61f481908b34cd24de88983c |
completed | April 19, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.