Triple
T38603635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Băile Olănești |
E934283
|
entity |
| Predicate | hasMineralWatersUsedFor |
P68556
|
FINISHED |
| Object | digestive disorders treatments |
—
|
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: digestive disorders treatments | Statement: [Băile Olănești, hasMineralWatersUsedFor, digestive disorders treatments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMineralWatersUsedFor Context triple: [Băile Olănești, hasMineralWatersUsedFor, digestive disorders treatments]
-
A.
hasCarbonatedWater
Indicates that an entity contains or is associated with carbonated (fizzy) water as a component or ingredient.
-
B.
mineralWaterCommercialisedBy
Indicates that a specific mineral water product is marketed, distributed, or sold by a particular commercial entity or company.
-
C.
hasWaterUse
chosen
Indicates a relationship where one entity utilizes or consumes water for a particular purpose, process, or function.
-
D.
hasSurroundingWatersUsedFor
Indicates that the surrounding waters of a place or area are utilized for a specific purpose or activity.
-
E.
hasMineralSprings
Indicates that a place or entity possesses or is characterized by the presence of mineral springs.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 3, 2026, 4:32 p.m.