Triple
T26561447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Range |
E666252
|
entity |
| Predicate | volcanicRockTypes |
P118514
|
FINISHED |
| Object | basaltic andesite |
—
|
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: basaltic andesite | Statement: [Emperor Range, volcanicRockTypes, basaltic andesite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volcanicRockTypes Context triple: [Emperor Range, volcanicRockTypes, basaltic andesite]
-
A.
volcanismType
Indicates the specific kind or style of volcanic activity or processes associated with an entity.
-
B.
volcanoComposition
chosen
Indicates that a volcano is composed of, or primarily made up of, a specified material or set of materials.
-
C.
volcanicOrigin
Indicates that something originates from, is produced by, or is directly associated with volcanic activity or processes.
-
D.
typicalLavaType
Indicates the usual or characteristic type of lava associated with a given volcanic feature, eruption, or context.
-
E.
typeOfVolcanicFeature
Indicates that one entity is classified as a specific kind or category of volcanic feature represented by the other entity.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6146c6e188190aa022ef2b9ee1774 |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 1:52 a.m.