Triple
T932969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dvaita |
E20133
|
entity |
| Predicate | considersSouls |
P6840
|
FINISHED |
| Object | dependent realities (paratantra) |
—
|
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: dependent realities (paratantra) | Statement: [Dvaita, considersSouls, dependent realities (paratantra)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: considersSouls Context triple: [Dvaita, considersSouls, dependent realities (paratantra)]
-
A.
viewOnSoul
chosen
Indicates a relationship where one entity holds or expresses a particular perspective, belief, or stance regarding the nature, existence, or characteristics of the soul.
-
B.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
C.
considersItself
Indicates that an entity regards or perceives itself in a particular way, role, or state.
-
D.
couldConsider
Indicates that one entity has the potential or option to take another entity into account when making a decision, judgment, or evaluation.
-
E.
UNConsiders
Indicates that the United Nations is formally examining, deliberating on, or taking into account a particular issue, proposal, or situation.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3bcad2481908b83575b2fb80d14 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b299c4d881908a57ac2711676cd7 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.