Triple
T31415961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rothaar Mountains foothills |
E801393
|
entity |
| Predicate | formsOuterRegionOf |
P10768
|
FINISHED |
| Object | Rothaar 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: Rothaar Mountains | Statement: [Rothaar Mountains foothills, formsOuterRegionOf, Rothaar Mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsOuterRegionOf Context triple: [Rothaar Mountains foothills, formsOuterRegionOf, Rothaar Mountains]
-
A.
formsRegionWith
Indicates that multiple entities combine or connect to constitute a single, continuous region.
-
B.
formationRegion
Indicates the place or area where something originates, is created, or comes into being.
-
C.
formsNaturalRegionWith
Indicates that two or more geographic entities together constitute or belong to the same continuous natural region or landscape unit.
-
D.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
E.
borderRegionOf
chosen
Indicates that one region lies along, touches, or forms part of the boundary of another region.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 30, 2026, 8:43 p.m.