Triple
T31873275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neustadt am Kulm |
E813666
|
entity |
| Predicate | hasNearbyVolcanicFeature |
P10443
|
FINISHED |
| Object | Rauher Kulm |
—
|
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: Rauher Kulm | Statement: [Neustadt am Kulm, hasNearbyVolcanicFeature, Rauher Kulm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyVolcanicFeature Context triple: [Neustadt am Kulm, hasNearbyVolcanicFeature, Rauher Kulm]
-
A.
isVolcanicNeighborOf
Indicates that one geographic feature is located close enough to another volcanic feature that they are considered neighboring volcano-related entities.
-
B.
nearVolcano
chosen
Indicates that one entity is located in close proximity to a volcano.
-
C.
volcanoTypeNearby
Indicates that one entity is located near another entity that is classified as a particular type of volcano.
-
D.
hasVolcanicLandform
Indicates that one entity possesses, contains, or is characterized by a volcanic landform (such as a volcano, caldera, or lava plateau).
-
E.
nearbyVolcanicComplexName
Indicates that an entity is associated with or located near a volcanic complex identified by a specific name.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
Created at: April 30, 2026, 11:55 p.m.