Triple
T37803131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatadage |
E942433
|
entity |
| Predicate | housedRelic |
P36131
|
FINISHED |
| Object | Sacred Tooth Relic of the Buddha |
—
|
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: Sacred Tooth Relic of the Buddha | Statement: [Hatadage, housedRelic, Sacred Tooth Relic of the Buddha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: housedRelic Context triple: [Hatadage, housedRelic, Sacred Tooth Relic of the Buddha]
-
A.
relicsLocatedIn
chosen
Indicates that certain relics are situated, stored, or found within a specific location.
-
B.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
-
C.
relicsAssociatedWith
Indicates a relationship where certain relics are connected or linked to a particular entity, context, or subject (such as a person, place, event, or tradition).
-
D.
holyRelicDisplayedOn
Indicates that a sacred or revered religious object is being publicly shown or exhibited on a particular surface, structure, or location.
-
E.
relicsDiscoveryYear
Indicates the year in which the relics were discovered.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.