Triple

T3242332
Position Surface form Disambiguated ID Type / Status
Subject Lake Bolsena E67989 entity
Predicate region P40 FINISHED
Object Tuscia E215443 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: Tuscia | Statement: [Lake Bolsena, region, Tuscia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tuscia
Context triple: [Lake Bolsena, region, Tuscia]
  • A. South Picene
    South Picene is an extinct ancient Italic language once spoken in central Italy and known primarily from a small corpus of archaic inscriptions.
  • B. Picenum
    Picenum was an ancient region on the Adriatic coast of central Italy, inhabited by the Picentes people and later incorporated into the Roman Republic.
  • C. Lanuvium
    Lanuvium was an ancient Latin city in central Italy, noted for its important sanctuary of Juno Sospita and its later incorporation into the Roman state.
  • D. Bracciano
    Bracciano is a historic town in the Lazio region of central Italy, known for its volcanic lake and the well-preserved Orsini-Odescalchi Castle.
  • E. Latium Adiectum chosen
    Latium Adiectum was the later-expanded part of ancient Latium in central Italy, added to the original Latin territory under Roman control.
  • 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_69ad858d27348190abb61c280b4c86a9 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69adaf17463481909447f6ab46016407 completed March 8, 2026, 5:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69b27757dff0819081a26aea52ede49d completed March 12, 2026, 8:20 a.m.
Created at: March 8, 2026, 3:08 p.m.