Triple
T34167060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zao Onsen |
E876439
|
entity |
| Predicate | onsenUse |
P178474
|
FINISHED |
| Object | therapeutic bathing |
—
|
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: therapeutic bathing | Statement: [Zao Onsen, onsenUse, therapeutic bathing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onsenUse Context triple: [Zao Onsen, onsenUse, therapeutic bathing]
-
A.
onsenArea
Indicates that a location or region is designated as an onsen (hot spring) area.
-
B.
onsenCategory
Indicates that one entity is classified as belonging to a particular category or type within the context of hot springs (onsen).
-
C.
hasOnsen
Indicates that one entity possesses, contains, or provides access to an onsen (hot spring bath).
-
D.
denUse
Indicates that an entity uses or makes use of a particular den (or designated shelter/space) for its activities or habitation.
-
E.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710aaff588190adc6cc5b7d5424cc |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fddd43c819088dee5a448c72cbe |
completed | May 3, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:54 a.m.