Triple
T11161996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jastrzębie-Zdrój |
E264057
|
entity |
| Predicate | wasSpaTown |
P98177
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Jastrzębie-Zdrój, wasSpaTown, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSpaTown Context triple: [Jastrzębie-Zdrój, wasSpaTown, 19th century]
-
A.
hasSpaTown
Indicates that a place is associated with or contains a town known for its spa or therapeutic bathing facilities.
-
B.
isSpaTownOf
Indicates that a place is recognized as a spa town belonging to, or located within the jurisdiction of, a specified larger administrative area or region.
-
C.
hasSpaResort
Indicates that one entity possesses, includes, or is associated with a spa resort as an amenity or feature.
-
D.
isResortTown
Indicates that a town functions primarily as a resort destination, typically focused on tourism, leisure, and vacation activities.
-
E.
hasThermalBathsSince
Indicates that an entity has had thermal baths available or in operation continuously since a specified point in time.
- F. None of above. chosen
Provenance (4 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8832fe88190a74d81f9ed547baa |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d7706116248190a87440bec3960884 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.