Triple
T30862507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberwaltersdorf |
E786098
|
entity |
| Predicate | hasLeisureFacilities |
P5383
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Oberwaltersdorf, hasLeisureFacilities, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeisureFacilities Context triple: [Oberwaltersdorf, hasLeisureFacilities, true]
-
A.
hasRecreationFacility
Indicates that one entity provides, contains, or is equipped with a recreational facility for use by another entity or by the public.
-
B.
hasRecreationalArea
chosen
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
C.
isRecreationalFacility
Indicates that the subject entity functions as a place or installation intended for leisure, sports, or other recreational activities.
-
D.
hasCivicAmenity
Indicates that an entity possesses, provides, or is associated with a public facility or service intended for community use.
-
E.
hasRegionalAmenity
Indicates that a region provides or contains a specific amenity or facility within its area.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 29, 2026, 8:47 p.m.