Triple
T24572557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nymphaeum of Alexander Severus |
E608000
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman nymphaeum |
C6381
|
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: ancient Roman nymphaeum Context triple: [Nymphaeum of Alexander Severus, instanceOf, ancient Roman nymphaeum]
-
A.
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.
-
B.
ancient cistern
An ancient cistern is a large, often subterranean, man-made reservoir designed to collect, store, and preserve water for a settlement or structure in antiquity.
-
C.
ancient Roman monument
chosen
An ancient Roman monument is a large, enduring structure or commemorative work built by the Romans to honor deities, leaders, victories, or civic achievements, often showcasing advanced engineering and classical architectural styles.
-
D.
ancient Roman tunnel
An ancient Roman tunnel is an underground passage engineered by the Romans, typically cut through rock or earth, to facilitate transportation, water conveyance, or drainage within their expansive infrastructure networks.
-
E.
ancient Roman temple
An ancient Roman temple is a monumental religious structure, typically rectangular with a columned portico and elevated podium, dedicated to one or more deities and serving as a focal point for public worship and civic identity in Roman society.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:28 a.m.