Triple
T31942925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kwannon |
E815573
|
entity |
| Predicate | equivalentInSanskrit |
P20185
|
FINISHED |
| Object | Avalokiteśvara |
—
|
NE NERFINISHED |
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: Avalokiteśvara | Statement: [Kwannon, equivalentInSanskrit, Avalokiteśvara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentInSanskrit Context triple: [Kwannon, equivalentInSanskrit, Avalokiteśvara]
-
A.
hasMeaningInSanskrit
Indicates that one entity (such as a word, phrase, or symbol) possesses a specific meaning when interpreted in the Sanskrit language.
-
B.
equivalentInTibet
Indicates that two entities are considered equivalent or correspond to each other within the context of Tibet.
-
C.
thaatEquivalentInHindustani
Indicates that two musical elements are equivalent or correspond to the same thaat (parent scale) within the Hindustani music system.
-
D.
equivalentInBuddhism
chosen
Indicates that one concept, figure, or element is regarded as the corresponding or matching counterpart within the context of Buddhism.
-
E.
equivalentEnglishForm
Indicates that two expressions share the same meaning in English, serving as equivalent linguistic forms.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 12:06 a.m.