Triple
T14937961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anjar |
E372444
|
entity |
| Predicate | sufferedHeavyDamageIn |
P992
|
FINISHED |
| Object | 2001 Gujarat earthquake |
—
|
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: 2001 Gujarat earthquake | Statement: [Anjar, sufferedHeavyDamageIn, 2001 Gujarat earthquake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedHeavyDamageIn Context triple: [Anjar, sufferedHeavyDamageIn, 2001 Gujarat earthquake]
-
A.
tookHeavyDamageAt
Indicates that an entity experienced severe or substantial damage at a specific location or point in time.
-
B.
sufferedDamageTo
Indicates that one entity has experienced harm, loss, or deterioration affecting another entity or one of its parts.
-
C.
damagedBy
Indicates that one entity has caused harm, impairment, or deterioration to another entity.
-
D.
damageTo
Indicates a relationship where one entity causes harm, loss, or deterioration to another entity.
-
E.
damagedIn
chosen
Indicates that an entity has suffered harm, impairment, or destruction as a result of a specified event, process, or condition.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64904d88190b6b4140da8e8199d |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:38 a.m.