Triple
T16769503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rano Aroi |
E407554
|
entity |
| Predicate | hasFormationType |
P23125
|
FINISHED |
| Object | volcanic activity |
—
|
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: volcanic activity | Statement: [Rano Aroi, hasFormationType, volcanic activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormationType Context triple: [Rano Aroi, hasFormationType, volcanic activity]
-
A.
containsFormation
Indicates that one entity spatially or structurally includes or encloses a formation as part of its extent or composition.
-
B.
isFormedFor
Indicates that something is created, established, or brought into existence for a particular purpose, function, or beneficiary.
-
C.
hasFieldFormation
Indicates that an entity possesses or exhibits a particular field formation, such as a structured arrangement or configuration of fields.
-
D.
formationType
chosen
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
-
E.
hasFormulationType
Indicates the specific way something is physically prepared or presented, such as its dosage form, composition, or delivery format.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b0356a9c8190b316cd00223e7537 |
completed | April 18, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.