Triple
T17982327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishva Hindu Parishad |
E449630
|
entity |
| Predicate | positionOnAyodhya |
P130001
|
FINISHED |
| Object | supports construction of Ram temple at disputed site |
—
|
LITERAL 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: supports construction of Ram temple at disputed site | Statement: [Vishva Hindu Parishad, positionOnAyodhya, supports construction of Ram temple at disputed site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnAyodhya Context triple: [Vishva Hindu Parishad, positionOnAyodhya, supports construction of Ram temple at disputed site]
-
A.
distanceToAyodhya
Indicates the measured spatial distance between a given entity’s location and the location of Ayodhya.
-
B.
positionInVeda
Indicates the specific location or ordering of a referenced element within the structure of a Vedic text.
-
C.
positionWithinAnandSahib
Indicates that one entity occupies a specific location or segment within the Anand Sahib text or structure.
-
D.
positionInTemple
Indicates the specific location or role an entity occupies within a temple.
-
E.
positionOfStatue
Indicates the spatial location where a statue is situated or placed.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b297b7108190a676409b330ca23b |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.