Triple
T21348596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drift River |
E526408
|
entity |
| Predicate | hasVolcanicLaharHistory |
P95449
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Drift River, hasVolcanicLaharHistory, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolcanicLaharHistory Context triple: [Drift River, hasVolcanicLaharHistory, true]
-
A.
hasLahars
chosen
Indicates that an entity experiences, produces, or is associated with volcanic mudflows (lahars).
-
B.
hasPotentialForLahars
Indicates that one entity (typically a geographic or volcanic feature) is capable of producing or being affected by lahars under certain conditions.
-
C.
hasHistoricalEruptionsSince
Indicates that the referenced volcano or geological feature has experienced one or more recorded eruptions since a specified point in time.
-
D.
hasVolcanicProduct
Indicates that an entity possesses, contains, or is associated with material or products originating from volcanic activity.
-
E.
hasFrequentEruptionsSince
Indicates that an entity has experienced eruptions repeatedly and at relatively short intervals starting from a specified point in time.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee5baab4e081908916a289c607cf3a |
completed | April 26, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:02 p.m.