Triple
T21553428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hualālai Northwest Rift Zone |
E531823
|
entity |
| Predicate | associatedWithHotspot |
P38067
|
FINISHED |
| Object | Hawaiian hotspot |
—
|
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: Hawaiian hotspot | Statement: [Hualālai Northwest Rift Zone, associatedWithHotspot, Hawaiian hotspot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithHotspot Context triple: [Hualālai Northwest Rift Zone, associatedWithHotspot, Hawaiian hotspot]
-
A.
isHotspotTrackOf
chosen
Indicates that one entity is a hotspot track that corresponds to, or is derived from, another entity.
-
B.
hotspot
Indicates that a location or entity is a focal point of intense activity, interest, or occurrence relative to others.
-
C.
hotspotType
Indicates the specific category or kind of hotspot associated with an entity or location.
-
D.
isAccessPointOf
Indicates that one entity serves as an access point or entry interface through which another entity can be reached, used, or connected to.
-
E.
associatedWithHorizon
Indicates a relationship in which something is linked or connected to a horizon, boundary, or limiting context.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb594956c8190a5b4d81911e3927d |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.