Triple
T21725642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hualālai Southwest Rift Zone |
E536267
|
entity |
| Predicate | nearbySettlementImpactRisk |
P107920
|
FINISHED |
| Object | Kona district communities |
—
|
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: Kona district communities | Statement: [Hualālai Southwest Rift Zone, nearbySettlementImpactRisk, Kona district communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbySettlementImpactRisk Context triple: [Hualālai Southwest Rift Zone, nearbySettlementImpactRisk, Kona district communities]
-
A.
nearbySettlements
Indicates that one settlement is located close to another settlement in geographic space.
-
B.
nearbySettlementStatus
Indicates whether a settlement is located close enough to another reference point or area to be considered nearby.
-
C.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
-
D.
locatedNearHazard
Indicates that one entity is situated in close physical proximity to a hazardous object, area, or condition.
-
E.
nearbyInfluence
chosen
Indicates that one entity affects or exerts influence on another due to being physically or spatially close to it.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd972ed248190bd0d4ac43efccbfd |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.