Triple
T4782840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dashavatara |
E106405
|
entity |
| Predicate | variationNote |
P4680
|
FINISHED |
| Object | lists sometimes replace Buddha with Balarama |
—
|
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: lists sometimes replace Buddha with Balarama | Statement: [Dashavatara, variationNote, lists sometimes replace Buddha with Balarama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variationNote Context triple: [Dashavatara, variationNote, lists sometimes replace Buddha with Balarama]
-
A.
variant
chosen
Indicates that one entity is an alternative form, version, or variation of another entity.
-
B.
notableChange
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
C.
modification
Indicates a change made to an existing entity, altering its properties, structure, or state from a prior version.
-
D.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
E.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.