Triple
T23026844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ichino-yu |
E573338
|
entity |
| Predicate | hasBathingCulture |
P146648
|
FINISHED |
| Object | Japanese onsen etiquette |
—
|
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: Japanese onsen etiquette | Statement: [Ichino-yu, hasBathingCulture, Japanese onsen etiquette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBathingCulture Context triple: [Ichino-yu, hasBathingCulture, Japanese onsen etiquette]
-
A.
bathingTradition
chosen
Indicates a customary or culturally established way in which bathing is practiced or carried out.
-
B.
hasBathhouse
Indicates that one entity possesses, contains, or is associated with a bathhouse facility.
-
C.
typeOfBathingSite
Indicates the specific kind or category of bathing site associated with a given location or facility.
-
D.
hasOceanBaths
Indicates that a place or location contains or is equipped with ocean baths—man-made seawater pools or bathing facilities built along the coastline.
-
E.
hasSpaTradition
Indicates that an entity is associated with an established practice or culture of spa, wellness, or therapeutic bathing activities.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1847d7cb48190902169813c46a278 |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:52 p.m.