Triple
T34379930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Higashiyama Onsen |
E882405
|
entity |
| Predicate | bathingEtiquette |
P146648
|
FINISHED |
| Object | Japanese onsen etiquette applies |
—
|
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 applies | Statement: [Higashiyama Onsen, bathingEtiquette, Japanese onsen etiquette applies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bathingEtiquette Context triple: [Higashiyama Onsen, bathingEtiquette, Japanese onsen etiquette applies]
-
A.
bathingTradition
chosen
Indicates a customary or culturally established way in which bathing is practiced or carried out.
-
B.
typeOfBathingSite
Indicates the specific kind or category of bathing site associated with a given location or facility.
-
C.
requiresAblution
Indicates that performing the referenced action or participating in the referenced state or event is contingent upon first completing a ritual washing or purification (ablution).
-
D.
hasAblutionFacilities
Indicates that an entity provides or is equipped with facilities for performing ablution or ritual washing.
-
E.
hasBathhouse
Indicates that one entity possesses, contains, or is associated with a bathhouse facility.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
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:59 a.m.