Triple

T1985233
Position Surface form Disambiguated ID Type / Status
Subject Sidicini E43123 entity
Predicate relatedPeople P37 FINISHED
Object Aurunci E45395 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: Aurunci | Statement: [Sidicini, relatedPeople, Aurunci]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aurunci
Context triple: [Sidicini, relatedPeople, Aurunci]
  • A. Aurunci chosen
    The Aurunci were an ancient Italic people of south-central Italy, known from early Roman history and associated with the Oscan-speaking cultural sphere.
  • B. Vulci
    Vulci was an important ancient Etruscan city renowned for its rich tombs, art, and role in Mediterranean trade.
  • C. Marrucini
    The Marrucini were an ancient Italic tribe of central Italy, closely associated with neighboring peoples like the Marsi and Paeligni and later incorporated into the Roman state.
  • D. Clusium
    Clusium was an important ancient Etruscan city, known for its strategic location in central Italy and its significant role in early Roman history.
  • E. 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.
  • 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_69a88713ddc88190a969715658ebe7a8 completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abbdbe35688190ab99620859e071c6 completed March 7, 2026, 5:55 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae0ad53ccc8190b0e0f44cfddfe9a4 completed March 8, 2026, 11:48 p.m.
Created at: March 4, 2026, 7:37 p.m.