Triple
T3084931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ram Janmabhoomi |
E64347
|
entity |
| Predicate | demolitionEvent |
P35276
|
FINISHED |
| Object | demolition of Babri Masjid |
—
|
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: demolition of Babri Masjid | Statement: [Ram Janmabhoomi, demolitionEvent, demolition of Babri Masjid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demolitionEvent Context triple: [Ram Janmabhoomi, demolitionEvent, demolition of Babri Masjid]
-
A.
demolitionAnnounced
Indicates that an official announcement has been made that a demolition of something is planned or will take place.
-
B.
demolitionStart
Indicates the point in time when the process of demolishing a structure or object begins.
-
C.
demolitionEnd
Indicates the point in time or event at which a demolition process is completed or comes to an end.
-
D.
hasDemolitionOrDestruction
chosen
Indicates that one entity causes, undergoes, or is associated with the demolition or destruction of another entity.
-
E.
demolished
Indicates that one entity completely destroyed or razed another entity, typically a structure or object, so that it no longer exists in its previous form.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1e98a1c8190b1dd4a0a47f7d6c6 |
completed | March 8, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.