Triple
T25681347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java volcanic arc |
E643947
|
entity |
| Predicate | containsVolcanoes |
P6356
|
FINISHED |
| Object | active 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: active volcanoes | Statement: [Java volcanic arc, containsVolcanoes, active volcanoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsVolcanoes Context triple: [Java volcanic arc, containsVolcanoes, active volcanoes]
-
A.
hasVolcano
chosen
Indicates that one entity possesses, contains, or is the location of a volcano.
-
B.
hasVolcanicVents
Indicates that one entity possesses or contains volcanic vents associated with another entity or location.
-
C.
containsVolcanicRegion
Indicates that one entity geographically includes or encompasses an area characterized by volcanic features or activity.
-
D.
isVolcanic
Indicates that something is characterized by or related to volcanic activity, such as originating from, produced by, or associated with a volcano.
-
E.
numberOfVolcanoes
Indicates the count of volcanoes associated with a given entity or within a specified context.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 21, 2026, 7:59 p.m.