Triple
T34749040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khidrana |
E1001716
|
entity |
| Predicate | hasNearbyGurdwara |
P201314
|
FINISHED |
| Object | Gurdwara Tibbi Sahib (Muktsar) |
—
|
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: Gurdwara Tibbi Sahib (Muktsar) | Statement: [Khidrana, hasNearbyGurdwara, Gurdwara Tibbi Sahib (Muktsar)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyGurdwara Context triple: [Khidrana, hasNearbyGurdwara, Gurdwara Tibbi Sahib (Muktsar)]
-
A.
majorGurdwara
Indicates that a gurdwara holds major or primary religious, cultural, or historical significance relative to other gurdwaras.
-
B.
nearbyGhats
Indicates that one location is situated close to or in the immediate vicinity of a ghat (such as a riverfront or stepped embankment).
-
C.
nearbyIndianTown
Indicates that one location is a town in India situated close to the referenced place.
-
D.
hasApproximateOneWayDistanceFromIndianGarden
Indicates that there is an estimated or non-exact one-way distance from Indian Garden to another location.
-
E.
distanceFromGurugram_km
Indicates the physical distance, measured in kilometers, between an entity’s location and Gurugram.
- F. None of above. chosen
Provenance (4 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ffe8ebe9fc8190b1934a3c4074370c |
completed | May 10, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69ffe83a5de88190bed3e8bac86e8760 |
completed | May 10, 2026, 2:06 a.m. |
| PDg | Predicate description generation | batch_69ffe8eb47d48190acf7794ebe3ef4b8 |
completed | May 10, 2026, 2:09 a.m. |
Created at: May 3, 2026, 3:59 p.m.