Triple
T14968250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rakshastal |
E373247
|
entity |
| Predicate | opposedConceptuallyTo |
P21665
|
FINISHED |
| Object | purity of Lake Manasarovar |
—
|
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: purity of Lake Manasarovar | Statement: [Rakshastal, opposedConceptuallyTo, purity of Lake Manasarovar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedConceptuallyTo Context triple: [Rakshastal, opposedConceptuallyTo, purity of Lake Manasarovar]
-
A.
hasConceptualOpposite
chosen
Indicates that one entity represents a concept that is fundamentally opposed or contrary in meaning to the concept represented by another entity.
-
B.
opposite
Indicates that one entity is positioned or oriented directly across from, or in a contrary or reverse relation to, another entity.
-
C.
theoryOpposed
Indicates that one theory stands in opposition to, or conflicts with, another theory.
-
D.
opposedOperation
Indicates that one operation is in conflict with, counters, or works against another operation.
-
E.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6e44cb0819096e09f8026ef8174 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:48 a.m.