Triple
T31873267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neustadt am Kulm |
E813666
|
entity |
| Predicate | hasNearbyNaturalLandmark |
P194420
|
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, hasNearbyNaturalLandmark, Rauher Kulm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyNaturalLandmark Context triple: [Neustadt am Kulm, hasNearbyNaturalLandmark, Rauher Kulm]
-
A.
proximityToLandmark
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
B.
hasNaturalParkNearby
Indicates that one entity is located close to, or in the vicinity of, a natural park associated with the other entity.
-
C.
hasNaturalAttractionsNearby
chosen
Indicates that a place is located near or surrounded by notable natural attractions or scenic natural features.
-
D.
typicalNearbyLandmarks
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
-
E.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
- 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_69ff1c91bbac8190b84012dee1cb3b2c |
completed | May 9, 2026, 11:37 a.m. |
| PD | Predicate disambiguation | batch_69ff1c23ca508190bb5a435d765b7e53 |
completed | May 9, 2026, 11:36 a.m. |
Created at: April 30, 2026, 11:55 p.m.