Triple
T25812108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umbul Binangun bathing pool |
E650138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | royal bathing pool |
C34534
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: royal bathing pool Context triple: [Umbul Binangun bathing pool, instanceOf, royal bathing pool]
-
A.
royal pavilion
A royal pavilion is an ornate, often temporary or semi-permanent structure used by royalty for ceremonial, recreational, or representational purposes, typically featuring luxurious design and prominent placement within palace grounds or formal landscapes.
-
B.
royal hammam
chosen
A royal hammam is an opulent, palace-affiliated bathhouse designed for ritual cleansing, relaxation, and socializing among nobility, often featuring elaborate architecture, heated marble rooms, and luxurious amenities.
-
C.
royal stables complex
A royal stables complex is an organized ensemble of buildings and yards designed to house, train, and maintain horses and related equipment for a royal household’s transportation, ceremonial, and military needs.
-
D.
royal retreat
A royal retreat is an exclusive, often secluded residence or estate where members of a royal family withdraw from public duties to rest, reflect, and conduct private affairs in a luxurious and secure setting.
-
E.
ancient Roman bath
An ancient Roman bath is a public complex of interconnected rooms and pools designed for bathing, socializing, exercise, and relaxation, typically featuring heated and cold baths, steam rooms, and elaborate architectural decoration.
- F. None of above.
Provenance (1 batch)
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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:11 a.m.