Triple
T35429125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Relic Stupa of Buddha at Vaishali |
E1024004
|
entity |
| Predicate | hasSacredRelicsType |
P63949
|
FINISHED |
| Object | Buddha’s corporeal relics (mortal remains) |
—
|
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: Buddha’s corporeal relics (mortal remains) | Statement: [Relic Stupa of Buddha at Vaishali, hasSacredRelicsType, Buddha’s corporeal relics (mortal remains)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredRelicsType Context triple: [Relic Stupa of Buddha at Vaishali, hasSacredRelicsType, Buddha’s corporeal relics (mortal remains)]
-
A.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
B.
hasRelicsStatus
Indicates that an entity holds a particular status or condition specifically related to relics.
-
C.
hasRelicType
chosen
Indicates that an entity is associated with, classified by, or possesses a specific type or category of relic.
-
D.
hasSacredWeapon
Indicates that an entity possesses or is associated with a weapon regarded as holy, consecrated, or religiously significant.
-
E.
containsRelic
Indicates that one entity holds, includes, or has within it a relic.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:03 p.m.