Triple
T7525375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pashupatinath Temple |
E177876
|
entity |
| Predicate | postEarthquakeStatus |
P60365
|
FINISHED |
| Object | main temple largely unharmed |
—
|
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: main temple largely unharmed | Statement: [Pashupatinath Temple, postEarthquakeStatus, main temple largely unharmed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postEarthquakeStatus Context triple: [Pashupatinath Temple, postEarthquakeStatus, main temple largely unharmed]
-
A.
postDisasterStatus
chosen
Indicates the condition or state of an entity following the occurrence of a disaster.
-
B.
hasEarthquakes
Indicates that the specified location or region experiences one or more earthquakes.
-
C.
statusAfter2015Earthquake
Indicates the condition or state of something following the 2015 earthquake.
-
D.
locationDuringEarthquake
Indicates the place where an entity is situated at the time an earthquake occurs.
-
E.
notableEarthquake
Indicates that an earthquake event is significant or noteworthy due to its magnitude, impact, or historical importance.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f7c7ac5c8190bbf9befdff791de0 |
completed | March 27, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:46 p.m.