Triple
T37970557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guru Tegh Bahadur |
E947270
|
entity |
| Predicate | associatedGurdwara |
P204499
|
FINISHED |
| Object | Gurdwara Sis Ganj Sahib |
E351445
|
NE 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: Gurdwara Sis Ganj Sahib | Statement: [Guru Tegh Bahadur, associatedGurdwara, Gurdwara Sis Ganj Sahib]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedGurdwara Context triple: [Guru Tegh Bahadur, associatedGurdwara, Gurdwara Sis Ganj Sahib]
-
A.
majorGurdwara
Indicates that a gurdwara holds major or primary religious, cultural, or historical significance relative to other gurdwaras.
-
B.
hasNearbyGurdwara
Indicates that one entity is located close to a gurdwara (a Sikh place of worship).
-
C.
associatedWithGharana
Indicates a relationship where an entity is linked or connected to a particular gharana (a specific musical or artistic lineage or school).
-
D.
valueInSikhism
Indicates that something holds a particular religious, moral, or cultural significance within the beliefs, practices, or teachings of Sikhism.
-
E.
hasAshramaAt
Indicates that an ashrama (hermitage or spiritual retreat) is located at or associated with a specific place.
- F. None of above. chosen
Provenance (5 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41b2845bcc8190bf5aa83f1f7bf6a4 |
completed | June 28, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:20 p.m.