Triple
T25693344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shrinathji |
E644254
|
entity |
| Predicate | principalTemple |
P8490
|
FINISHED |
| Object | Shrinathji Temple, Nathdwara |
—
|
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: Shrinathji Temple, Nathdwara | Statement: [Shrinathji, principalTemple, Shrinathji Temple, Nathdwara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalTemple Context triple: [Shrinathji, principalTemple, Shrinathji Temple, Nathdwara]
-
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.
elementRepresentedByMainTemple
Indicates that a particular element is symbolized or embodied by the main temple in a given religious or cultural context.
-
D.
templeState
Indicates that a temple is in a particular condition, status, or phase (such as operational, under construction, abandoned, or ceremonial).
-
E.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 8:31 p.m.