Triple
T27537269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comoros archipelago volcanic chain |
E695129
|
entity |
| Predicate | hasYoungestVolcanismOn |
P23548
|
FINISHED |
| Object | Grande Comore |
—
|
NE NERFINISHED |
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: Grande Comore | Statement: [Comoros archipelago volcanic chain, hasYoungestVolcanismOn, Grande Comore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYoungestVolcanismOn Context triple: [Comoros archipelago volcanic chain, hasYoungestVolcanismOn, Grande Comore]
-
A.
youngestVolcanismLocation
chosen
Indicates the location where the most recent or youngest volcanic activity associated with an entity occurs or is observed.
-
B.
isHoloceneVolcano
Indicates that a volcano has been active at least once during the Holocene epoch (approximately the last 11,700 years).
-
C.
oneOfMostActiveVolcanoesIn
Indicates that a volcano is among the most active volcanoes located within a specified geographic area or region.
-
D.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
E.
isYoungVolcanoInChain
Indicates that a volcano is among the younger members within a specific volcanic chain or arc.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:29 p.m.