Triple
T35356402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lac de Nantua |
E1021343
|
entity |
| Predicate | waterSportsPermitted |
P106010
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lac de Nantua, waterSportsPermitted, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterSportsPermitted Context triple: [Lac de Nantua, waterSportsPermitted, yes]
-
A.
boatingAllowed
Indicates that operating or using boats is permitted in the specified area or context.
-
B.
waterSport
Indicates participation in or association with a sport or recreational activity that takes place on or in water.
-
C.
swimmingAllowed
Indicates that swimming is permitted at a particular place, time, or under specified conditions.
-
D.
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).
-
E.
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).
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 3, 2026, 4:03 p.m.