Triple

T13325738
Position Surface form Disambiguated ID Type / Status
Subject Roman aqueduct E317436 entity
Predicate notableExample P1503 FINISHED
Object Aqua Virgo E539880 NE 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: Aqua Virgo | Statement: [Roman aqueduct, notableExample, Aqua Virgo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aqua Virgo
Context triple: [Roman aqueduct, notableExample, Aqua Virgo]
  • A. Aqua Virgo chosen
    Aqua Virgo is one of ancient Rome’s principal aqueducts, renowned for supplying water to the city and still partially functioning today as the source of the Trevi Fountain.
  • B. Aqua Appia
    Aqua Appia was one of ancient Rome’s earliest aqueducts, constructed in the 4th century BCE to supply the city with fresh water.
  • C. Aqua Anio Vetus
    Aqua Anio Vetus was one of ancient Rome’s earliest major aqueducts, channeling water from the Aniene River to supply the growing city.
  • D. Hydrus
    Hydrus is a small, faint constellation in the southern sky, often referred to as the "lesser water snake."
  • E. Acqua Vergine
    Acqua Vergine is a historic Roman aqueduct system, still in use today, that supplies water to several famous fountains in Rome, including the Trevi Fountain.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d806b4d62c81908d4ced1665414be5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d9992d3b0881909732fbb8db98e44c completed April 11, 2026, 12:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7266cfb3c8190ac9ccb7696d02922 completed May 3, 2026, 10:41 a.m.
Created at: April 9, 2026, 9:30 p.m.