Triple
T16732436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shishkat village |
E406623
|
entity |
| Predicate | economicActivityBeforeDisaster |
P114644
|
FINISHED |
| Object | agriculture |
—
|
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: agriculture | Statement: [Shishkat village, economicActivityBeforeDisaster, agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicActivityBeforeDisaster Context triple: [Shishkat village, economicActivityBeforeDisaster, agriculture]
-
A.
formerEconomicActivity
Indicates that an entity previously engaged in a specified economic activity but no longer does so.
-
B.
regionalEconomyActivity
chosen
Indicates the type or level of economic activity occurring within a specific geographic region.
-
C.
economicImpactRegion
Indicates the region or geographic area that experiences or is affected by a particular economic impact.
-
D.
preEruptionEconomy
Indicates the state or characteristics of an economy during the period immediately before a volcanic eruption or similar disruptive event.
-
E.
economicDamage
Indicates that one entity causes or experiences financial loss, harm, or negative economic impact as a result of another entity or event.
- 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_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. |
Created at: April 10, 2026, 5:20 a.m.