Triple
T37494953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varaha Temple, Pushkar |
E931799
|
entity |
| Predicate | isInHolyTown |
P88075
|
FINISHED |
| Object | Pushkar |
—
|
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: Pushkar | Statement: [Varaha Temple, Pushkar, isInHolyTown, Pushkar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInHolyTown Context triple: [Varaha Temple, Pushkar, isInHolyTown, Pushkar]
-
A.
locatedInHolyTown
chosen
Indicates that an entity is situated within a town that is considered holy or religiously significant.
-
B.
containsPilgrimageTown
Indicates that a place or region includes within its boundaries a town that serves as a destination or center for religious pilgrimage.
-
C.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
D.
isInFortifiedTown
Indicates that an entity is located within a town that is protected by defensive structures or fortifications.
-
E.
holyCityFor
Indicates that a city holds recognized religious significance or sacred status for a particular religion or religious community.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.