Triple
T32402278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summit crater Arenas |
E827983
|
entity |
| Predicate | nearbySettlementAtRisk |
P195100
|
FINISHED |
| Object | Armero (destroyed in 1985) |
—
|
NE NERFINISHED |
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: Armero (destroyed in 1985) | Statement: [Summit crater Arenas, nearbySettlementAtRisk, Armero (destroyed in 1985)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbySettlementAtRisk Context triple: [Summit crater Arenas, nearbySettlementAtRisk, Armero (destroyed in 1985)]
-
A.
nearbySettlements
Indicates that one settlement is located close to another settlement in geographic space.
-
B.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
-
C.
nearbySettlementStatus
Indicates whether a settlement is located close enough to another reference point or area to be considered nearby.
-
D.
nearbySettlementUS
Indicates that one settlement is geographically close to another settlement within the United States.
-
E.
hasNearestLargerSettlement
Indicates that one settlement is associated with the geographically closest settlement that is larger in size or population.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
| PDg | Predicate description generation | batch_69fda4fe67a08190bdaa84ceabd6de6c |
completed | May 8, 2026, 8:55 a.m. |
Created at: May 1, 2026, 12:52 a.m.