Triple
T16479618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quezaltepeque |
E400279
|
entity |
| Predicate | hasHumanImpactHistory |
P37550
|
FINISHED |
| Object | past eruptions affected nearby settlements |
—
|
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: past eruptions affected nearby settlements | Statement: [Quezaltepeque, hasHumanImpactHistory, past eruptions affected nearby settlements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHumanImpactHistory Context triple: [Quezaltepeque, hasHumanImpactHistory, past eruptions affected nearby settlements]
-
A.
hasEnvironmentalHistory
Indicates that an entity is associated with a record or account of its past environmental conditions, impacts, or interactions.
-
B.
facedHistoricalImpact
Indicates that an entity has experienced or been subjected to a significant influence, consequence, or change resulting from historical events or processes.
-
C.
hasHistoryOf
chosen
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
D.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
E.
hasInfrastructureHistory
Indicates that there exists a record or account of past changes, developments, or states of infrastructure associated with an entity.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e01f6c88190b75a0d6c94786426 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.