Triple

T1985197
Position Surface form Disambiguated ID Type / Status
Subject Sidicini E43123 entity
Predicate languageFamily P1047 FINISHED
Object Oscan E6805 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: Oscan | Statement: [Sidicini, languageFamily, Oscan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oscan
Context triple: [Sidicini, languageFamily, Oscan]
  • A. Oscan language chosen
    The Oscan language was an extinct Italic language once spoken by the Samnites and other peoples of southern Italy, closely related to Latin and Umbrian.
  • B. Faliscan
    Faliscan was an ancient Italic language closely related to Latin, once spoken in central Italy by the Falisci people.
  • C. Bruttians
    The Bruttians were an ancient Italic people of southern Italy, known for their role in regional conflicts during the Hellenistic and Roman periods.
  • D. Samnites
    The Samnites were an ancient Italic people of south-central Italy, known for their fierce resistance against Roman expansion during the Samnite Wars.
  • E. Siculian
    Siculian is an ancient Indo-European language once spoken by the Sicels in eastern Sicily.
  • 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_69abb821c2d48190abea6c89f37b51b1 completed March 7, 2026, 5:31 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.