Triple
T15729302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akan Onsen |
E381298
|
entity |
| Predicate | hasFootBaths |
P68523
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Akan Onsen, hasFootBaths, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFootBaths Context triple: [Akan Onsen, hasFootBaths, yes]
-
A.
hasBathhouse
chosen
Indicates that one entity possesses, contains, or is associated with a bathhouse facility.
-
B.
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.
-
C.
requiresShoesOff
Indicates that one entity mandates another to remove their shoes, typically as a condition for entry or participation.
-
D.
hasWaterActivity
Indicates that one entity possesses, exhibits, or is characterized by a particular level or type of water-related activity (such as moisture content, water availability, or water-based processes).
-
E.
hasFootstomps
Indicates that one entity performs or possesses foot-stomping actions or behaviors in relation to another entity or context.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb4cc0081909efe330339474017 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.