Triple
T9765229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poděbrady |
E236769
|
entity |
| Predicate | hasMineralWater |
P85830
|
FINISHED |
| Object | carbonated mineral springs |
—
|
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: carbonated mineral springs | Statement: [Poděbrady, hasMineralWater, carbonated mineral springs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMineralWater Context triple: [Poděbrady, hasMineralWater, carbonated mineral springs]
-
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.
hasMineralSprings
chosen
Indicates that a place or entity possesses or is characterized by the presence of mineral springs.
-
D.
hasMineralSpringsType
Indicates that an entity is associated with or characterized by a specific type or category of mineral springs.
-
E.
hasMineral
Indicates that one entity contains, includes, or is composed of a specified mineral.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0a040988190b1c940f9e5c42f9c |
completed | April 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.