Triple
T14918419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jachthuis Sint Hubertus |
E371442
|
entity |
| Predicate | situatedInLandscape |
P89452
|
FINISHED |
| Object | forested heathland |
—
|
LITERAL FINISHED |
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: forested heathland | Statement: [Jachthuis Sint Hubertus, situatedInLandscape, forested heathland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: situatedInLandscape Context triple: [Jachthuis Sint Hubertus, situatedInLandscape, forested heathland]
-
A.
isPartOfScenicVista
Indicates that something is included within, or contributes to, a larger scenic vista or panoramic view.
-
B.
situatedAmong
Indicates that an entity is located within or surrounded by multiple other entities in its immediate environment.
-
C.
landscapeElement
Indicates that one entity functions as a landscape-related feature or component in relation to another entity.
-
D.
locatedInParkLikeSetting
chosen
Indicates that something is situated within or directly surrounded by an environment resembling a park, typically featuring natural or landscaped outdoor elements.
-
E.
landscapeStyle
Indicates the design style or aesthetic approach applied to a landscape or outdoor environment.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded62f76bc81909ebc8899096cd1a0 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:33 a.m.