Triple
T20632160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kleinhesseloher See |
E506980
|
entity |
| Predicate | isSwimmingAllowed |
P39236
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Kleinhesseloher See, isSwimmingAllowed, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSwimmingAllowed Context triple: [Kleinhesseloher See, isSwimmingAllowed, false]
-
A.
swimmingAllowed
chosen
Indicates that swimming is permitted at a particular place, time, or under specified conditions.
-
B.
requiresSwimAbility
Indicates that one entity must possess the ability to swim as a necessary condition for participation in, access to, or compatibility with another entity or activity.
-
C.
canSwim
Indicates that an entity has the ability to move through water by swimming.
-
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.
swimmingAdvised
Indicates that engaging in swimming is recommended or suggested under certain conditions or for certain individuals.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad0bdcd88190a59d68e03370b271 |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 16, 2026, 11:42 a.m.