Triple
T34351730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillebachsee |
E881597
|
entity |
| Predicate | waterSportsAllowed |
P106010
|
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: [Hillebachsee, waterSportsAllowed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterSportsAllowed Context triple: [Hillebachsee, waterSportsAllowed, true]
-
A.
waterSport
Indicates participation in or association with a sport or recreational activity that takes place on or in water.
-
B.
boatingAllowed
Indicates that operating or using boats is permitted in the specified area or context.
-
C.
swimmingAllowed
Indicates that swimming is permitted at a particular place, time, or under specified conditions.
-
D.
hasWaterActivity
Indicates that one entity possesses, exhibits, or is characterized by a particular level or type of water-related activity (such as moisture content, water availability, or water-based processes).
-
E.
hasWaterRelatedActivity
chosen
Indicates that an entity engages in, offers, or is associated with an activity involving water (e.g., swimming, boating, or other water-based actions).
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 1, 2026, 1:58 a.m.