Triple
T1803051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamunotri |
E39760
|
entity |
| Predicate | templeOpening |
P32544
|
FINISHED |
| Object | on Akshaya Tritiya |
—
|
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: on Akshaya Tritiya | Statement: [Yamunotri, templeOpening, on Akshaya Tritiya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeOpening Context triple: [Yamunotri, templeOpening, on Akshaya Tritiya]
-
A.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
B.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
C.
lastMajorTempleClosed
Indicates the time or event at which the final significant temple associated with an entity was permanently closed.
-
D.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
E.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified place.
- F. None of above. chosen
Provenance (4 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_69a88632aa588190ba3978fde0db5bbd |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba67721788190951beae25e885457 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61d514c081908197ac1f7c7d7a88 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aba67554788190b429f2b9f0a70310 |
completed | March 7, 2026, 4:15 a.m. |
Created at: March 4, 2026, 7:32 p.m.