Triple

T3265659
Position Surface form Disambiguated ID Type / Status
Subject Sejanus E68521 entity
Predicate birthPlace P1 FINISHED
Object Volsinii E94670 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: Volsinii | Statement: [Sejanus, birthPlace, Volsinii]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Volsinii
Context triple: [Sejanus, birthPlace, Volsinii]
  • A. Volsci
    The Volsci were an ancient Italic tribe of central Italy, known primarily for their frequent conflicts with the early Roman Republic during the 5th and 4th centuries BCE.
  • B. Vulci chosen
    Vulci was an important ancient Etruscan city renowned for its rich tombs, art, and role in Mediterranean trade.
  • C. Clusium
    Clusium was an important ancient Etruscan city, known for its strategic location in central Italy and its significant role in early Roman history.
  • D. Aurunci
    The Aurunci were an ancient Italic people of south-central Italy, known from early Roman history and associated with the Oscan-speaking cultural sphere.
  • E. Falisci
    The Falisci were an ancient Italic people of central Italy, closely related to the Etruscans and known for their distinctive language and culture centered around the city of Falerii.
  • 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_69ad8590444081909e8107a8aeef3a23 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adafcc99908190897230b4b71e2ea8 completed March 8, 2026, 5:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69b2f3c4323c819087a7c6e6c8a7b030 completed March 12, 2026, 5:11 p.m.
Created at: March 8, 2026, 3:09 p.m.