Triple
T30820496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East African Volcanic Province |
E784905
|
entity |
| Predicate | hasVolcanicLandform |
P178826
|
FINISHED |
| Object | shield volcanoes |
—
|
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: shield volcanoes | Statement: [East African Volcanic Province, hasVolcanicLandform, shield volcanoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolcanicLandform Context triple: [East African Volcanic Province, hasVolcanicLandform, shield volcanoes]
-
A.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
B.
isVolcanic
Indicates that something is characterized by or related to volcanic activity, such as originating from, produced by, or associated with a volcano.
-
C.
hasVolcanicVents
Indicates that one entity possesses or contains volcanic vents associated with another entity or location.
-
D.
containsVolcanicRegion
Indicates that one entity geographically includes or encompasses an area characterized by volcanic features or activity.
-
E.
isVolcanicEdificeOn
Indicates that a volcanic edifice is physically located on or built upon a specified surface or geological feature.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 29, 2026, 8:44 p.m.