Triple
T37645339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bamus |
E937019
|
entity |
| Predicate | proximityToOtherVolcano |
P10443
|
FINISHED |
| Object | near the more prominent Ulawun volcano |
—
|
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: near the more prominent Ulawun volcano | Statement: [Bamus, proximityToOtherVolcano, near the more prominent Ulawun volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proximityToOtherVolcano Context triple: [Bamus, proximityToOtherVolcano, near the more prominent Ulawun volcano]
-
A.
nearVolcano
chosen
Indicates that one entity is located in close proximity to a volcano.
-
B.
volcanoTypeNearby
Indicates that one entity is located near another entity that is classified as a particular type of volcano.
-
C.
isVolcanicNeighborOf
Indicates that one geographic feature is located close enough to another volcanic feature that they are considered neighboring volcano-related entities.
-
D.
distanceFromVesuvius
Indicates the spatial distance between an entity and Mount Vesuvius.
-
E.
associatedVolcano
Indicates that there is a specific volcano linked or connected to the referenced entity, such as by location, impact, or relevance.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.