Triple

T3874594
Position Surface form Disambiguated ID Type / Status
Subject Antonine Baths E92469 entity
Predicate instanceOf P0 FINISHED
Object Roman public bath C6858 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: Roman public bath
Context triple: [Antonine Baths, instanceOf, Roman public bath]
  • A. 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.
  • B. ancient Roman monument
    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.
  • C. ancient Greek public building
    An ancient Greek public building is a communal structure, such as a temple, stoa, theater, or council house, designed to serve civic, religious, political, or social functions within the polis.
  • D. ancient Roman structure chosen
    An ancient Roman structure is a man-made construction from the Roman civilization, such as temples, amphitheaters, aqueducts, or baths, characterized by advanced engineering, arches, and durable materials like stone and concrete.
  • E. ancient Roman street
    An ancient Roman street is a paved public thoroughfare, typically constructed of stone blocks with raised sidewalks, drainage systems, and often lined with shops, houses, and public buildings, facilitating movement, trade, and social interaction within Roman cities.
  • 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_69aed967448c819086c4b358d37b25aa completed March 9, 2026, 2:29 p.m.
Created at: March 9, 2026, 3:20 p.m.