Triple
T26977544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jagannath-centric Vaishnavism |
E679498
|
entity |
| Predicate | centralTemple |
P8490
|
FINISHED |
| Object | Shri Jagannath Temple, Puri |
—
|
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: Shri Jagannath Temple, Puri | Statement: [Jagannath-centric Vaishnavism, centralTemple, Shri Jagannath Temple, Puri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralTemple Context triple: [Jagannath-centric Vaishnavism, centralTemple, Shri Jagannath Temple, Puri]
-
A.
mainTemple
chosen
Indicates that one entity serves as the primary or central temple associated with another entity.
-
B.
mainTempleState
Indicates that a temple serves as the primary or central religious site within a particular state or region.
-
C.
templeState
Indicates that a temple is in a particular condition, status, or phase (such as operational, under construction, abandoned, or ceremonial).
-
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.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
- 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 27, 2026, 6:43 a.m.