Triple
T30941130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eggegebirge |
E788262
|
entity |
| Predicate | naturePark |
P46553
|
FINISHED |
| Object | Teutoburg Forest–Egge Hills Nature Park |
—
|
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: Teutoburg Forest–Egge Hills Nature Park | Statement: [Eggegebirge, naturePark, Teutoburg Forest–Egge Hills Nature Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: naturePark Context triple: [Eggegebirge, naturePark, Teutoburg Forest–Egge Hills Nature Park]
-
A.
naturalAttractionOf
Indicates a relationship where one entity is a natural feature or site that draws interest, attention, or visitors from another entity.
-
B.
naturalMonument
Indicates that something is designated as a natural monument, typically a protected natural feature of special scientific, cultural, or aesthetic significance.
-
C.
localNatureSite
Indicates that a location is designated as a natural site of local significance or interest.
-
D.
nationalPark
Indicates that a location is designated and managed as a national park by a governing authority.
-
E.
containsNaturalPark
chosen
Indicates that one entity geographically includes or encompasses a natural park within its boundaries.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 8:53 p.m.