Triple
T34360886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iizaka Onsen |
E881868
|
entity |
| Predicate | healingUse |
P40313
|
FINISHED |
| Object | bathing for relaxation |
—
|
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: bathing for relaxation | Statement: [Iizaka Onsen, healingUse, bathing for relaxation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healingUse Context triple: [Iizaka Onsen, healingUse, bathing for relaxation]
-
A.
typeOfHealing
Indicates the specific method or modality by which a healing process is carried out or achieved.
-
B.
sacramentOfHealing
Indicates a relationship in which a religious sacrament is administered to bring spiritual or physical healing to a person.
-
C.
medicinalUse
chosen
Indicates that one entity is used as a treatment or remedy for a disease, condition, or health-related purpose affecting another entity.
-
D.
viewOnHealing
Indicates a stance, belief, or perspective that an entity holds regarding the nature, process, or principles of healing.
-
E.
receivesSupernaturalHealingFrom
Indicates that one entity is restored to health or cured through a supernatural or miraculous intervention provided 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:58 a.m.