Triple
T23752309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goverdhan |
E587002
|
entity |
| Predicate | hasPilgrimageTown |
P57321
|
FINISHED |
| Object | Govardhan |
—
|
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: Govardhan | Statement: [Goverdhan, hasPilgrimageTown, Govardhan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilgrimageTown Context triple: [Goverdhan, hasPilgrimageTown, Govardhan]
-
A.
containsPilgrimageTown
chosen
Indicates that a place or region includes within its boundaries a town that serves as a destination or center for religious pilgrimage.
-
B.
hasPilgrimageRegion
Indicates that an entity is associated with a specific region that serves as the destination or location for its pilgrimage activities.
-
C.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
D.
hasPilgrimageChurch
Indicates that a location or entity possesses or is associated with a church that serves as a destination for religious pilgrimage.
-
E.
hasPilgrimageFrom
Indicates that a pilgrimage originates from or is undertaken starting at a specified location or source.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcc289e08190a8036bb16dd0220a |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:13 p.m.