Triple
T38095007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purkersdorf (Lower Austria) |
E951219
|
entity |
| Predicate | hasSignificantLandscape |
P7342
|
FINISHED |
| Object | Vienna Woods |
—
|
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: Vienna Woods | Statement: [Purkersdorf (Lower Austria), hasSignificantLandscape, Vienna Woods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantLandscape Context triple: [Purkersdorf (Lower Austria), hasSignificantLandscape, Vienna Woods]
-
A.
hasLandscapeFeatures
Indicates that an entity possesses or includes specific landscape-related characteristics or elements.
-
B.
hasLandscapeUse
Indicates that something is used or intended to be used within a landscape or landscaping context.
-
C.
hasLandscapeType
chosen
Indicates that an entity possesses or is characterized by a particular type or category of landscape.
-
D.
hasLandscapeInfluence
Indicates that one entity has shaped, altered, or significantly affected the characteristics, form, or development of a landscape.
-
E.
isPartOfLandscape
Indicates that something forms a component or feature within a larger landscape or natural 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 3, 2026, 4:21 p.m.