Triple
T28075048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neuhausen/Erzgeb. |
E709512
|
entity |
| Predicate | isPartOfMountainRangeRegion |
P24755
|
FINISHED |
| Object | Ore Mountains |
—
|
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: Ore Mountains | Statement: [Neuhausen/Erzgeb., isPartOfMountainRangeRegion, Ore Mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfMountainRangeRegion Context triple: [Neuhausen/Erzgeb., isPartOfMountainRangeRegion, Ore Mountains]
-
A.
locatedInMountainRangeRegion
chosen
Indicates that a place or geographic entity is situated within the area covered by a specific mountain range.
-
B.
isInValleyOrMountainRegion
Indicates that an entity is located within either a valley area or a mountainous region.
-
C.
originatesFromMountainRange
Indicates that something has its source or beginning in a specific mountain range.
-
D.
hasMountainRange
Indicates that one entity possesses, contains, or is geographically associated with a specific mountain range.
-
E.
mountainRange
Indicates that one entity is a mountain range that the other entity is part of, associated with, or located in.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 27, 2026, 8:48 p.m.