Triple
T13331935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jáchymov Spa |
E317594
|
entity |
| Predicate | usesWaterType |
P851
|
FINISHED |
| Object | radon-rich thermal water |
—
|
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: radon-rich thermal water | Statement: [Jáchymov Spa, usesWaterType, radon-rich thermal water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWaterType Context triple: [Jáchymov Spa, usesWaterType, radon-rich thermal water]
-
A.
waterType
chosen
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
-
B.
usesWaterTreatment
Indicates that an entity applies or relies on a water treatment process or system in its operations or activities.
-
C.
hasWaterUse
Indicates a relationship where one entity utilizes or consumes water for a particular purpose, process, or function.
-
D.
waterServiceType
Indicates the specific kind or category of water service provided or associated with an entity.
-
E.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9992fffa0819086610ae3bed2e2f9 |
completed | April 11, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:30 p.m.