Triple
T37327725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Schlema |
E926655
|
entity |
| Predicate | gainedSpaStatus |
P154730
|
FINISHED |
| Object | Kurort (spa) status in 20th 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: Kurort (spa) status in 20th century | Statement: [Bad Schlema, gainedSpaStatus, Kurort (spa) status in 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedSpaStatus Context triple: [Bad Schlema, gainedSpaStatus, Kurort (spa) status in 20th century]
-
A.
hasSpaStatusSince
Indicates that an entity has held a particular spa-related status continuously starting from a specified point in time.
-
B.
hasSpaStatusLocation
Indicates that an entity has a specific spa-related status associated with a particular location.
-
C.
gainedStatus
chosen
Indicates that an entity has acquired or achieved a particular status, condition, or role as a result of some event or process.
-
D.
statusGrantedOn
Indicates the date or time at which a particular status was officially conferred or became effective for an entity.
-
E.
acquiredStatusOf
Indicates that one entity has obtained, taken over, or assumed the status or condition previously held by another 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.