Triple
T33281798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlsbad, Czech Republic |
E852063
|
entity |
| Predicate | hasBalneologicalTraditionSince |
P146812
|
FINISHED |
| Object | 14th century |
—
|
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: 14th century | Statement: [Carlsbad, Czech Republic, hasBalneologicalTraditionSince, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBalneologicalTraditionSince Context triple: [Carlsbad, Czech Republic, hasBalneologicalTraditionSince, 14th century]
-
A.
hasThermalBathsSince
Indicates that an entity has had thermal baths available or in operation continuously since a specified point in time.
-
B.
hasSpaTradition
chosen
Indicates that an entity is associated with an established practice or culture of spa, wellness, or therapeutic bathing activities.
-
C.
bathingTradition
Indicates a customary or culturally established way in which bathing is practiced or carried out.
-
D.
hasNumberOfMineralSprings
Indicates the relationship that specifies how many mineral springs are associated with a given entity.
-
E.
hasNumberOfHotSprings
Indicates the quantity of hot springs associated with a given entity.
- 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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 1, 2026, 1:32 a.m.