Triple
T16732446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shishkat village |
E406623
|
entity |
| Predicate | preDisasterStatus |
P124431
|
FINISHED |
| Object | important settlement of Upper Hunza |
—
|
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: important settlement of Upper Hunza | Statement: [Shishkat village, preDisasterStatus, important settlement of Upper Hunza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preDisasterStatus Context triple: [Shishkat village, preDisasterStatus, important settlement of Upper Hunza]
-
A.
postDisasterStatus
Indicates the condition or state of an entity following the occurrence of a disaster.
-
B.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
C.
prewarStatus
Indicates the condition, role, or circumstances of an entity as they existed before a specific war or armed conflict.
-
D.
preContactStatus
Indicates the state or condition of an entity or relationship that existed prior to an initial contact or interaction.
-
E.
preparedBefore
Indicates that one entity was prepared or made ready at an earlier time than another entity.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3748d08190a57ae40f54aa63c4 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.