Triple

T16451914
Position Surface form Disambiguated ID Type / Status
Subject Regio IV Samnium E399571 entity
Predicate contains P35 FINISHED
Object Arpinum E194569 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: Arpinum | Statement: [Regio IV Samnium, contains, Arpinum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arpinum
Context triple: [Regio IV Samnium, contains, Arpinum]
  • A. Arpinum chosen
    Arpinum is an ancient Italian town in Latium best known as the birthplace of the Roman statesman and orator Cicero.
  • B. Picenum city
    Picenum city refers to an ancient urban center located in the historical Picenum region of central Italy, inhabited by the Picentes people before and during Roman rule.
  • C. Praeneste
    Praeneste was an ancient Italian city in Latium, famed for its monumental sanctuary of Fortuna Primigenia and its strategic position overlooking the Roman Campagna.
  • D. Asculum
    Asculum was an important ancient city in central Italy, historically serving as the chief urban center of the Piceni people.
  • E. Ferentinum
    Ferentinum was an ancient town in central Italy historically associated with the Hernici people and later integrated into the Roman sphere.
  • 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_69d87f2c6778819080fcfae53be8f12a completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32ce19344819083d323077b742bc3 completed April 18, 2026, 7:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0060746c308190b67ff7c4646e10de completed May 10, 2026, 10:39 a.m.
Created at: April 10, 2026, 5:10 a.m.