Triple
T4871304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kedarnath Temple |
E109089
|
entity |
| Predicate | postDisasterStatus |
P60365
|
FINISHED |
| Object | structure survived with limited damage |
—
|
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: structure survived with limited damage | Statement: [Kedarnath Temple, postDisasterStatus, structure survived with limited damage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postDisasterStatus Context triple: [Kedarnath Temple, postDisasterStatus, structure survived with limited damage]
-
A.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
B.
resultOfEmergency
Indicates that something occurs or exists as a direct consequence of an emergency situation or event.
-
C.
postConstitutionStatus
Indicates the legal or political status of an entity after the adoption or coming into force of a constitution.
-
D.
supportsDisasterType
Indicates that one entity is capable of handling, responding to, or being applicable to a specified type of disaster.
-
E.
hasReliefEffortFrom
Indicates that a party receives assistance or support through a relief effort provided by another party.
- 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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c28e56081908ee411ac94c3769e |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6ff731188190a9903602122d4ff9 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:27 p.m.