Triple

T14229273
Position Surface form Disambiguated ID Type / Status
Subject Asculum E352707 entity
Predicate hasAlternativeName P39 FINISHED
Object Asculum Picenum E352707 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: Asculum Picenum | Statement: [Asculum, hasAlternativeName, Asculum Picenum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Asculum Picenum
Context triple: [Asculum, hasAlternativeName, Asculum Picenum]
  • A. Asculum chosen
    Asculum was an important ancient city in central Italy, historically serving as the chief urban center of the Piceni people.
  • B. Arpinum
    Arpinum is an ancient Italian town in Latium best known as the birthplace of the Roman statesman and orator Cicero.
  • C. Ferentinum
    Ferentinum was an ancient town in central Italy historically associated with the Hernici people and later integrated into the Roman sphere.
  • 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. Vulci
    Vulci was an important ancient Etruscan city renowned for its rich tombs, art, and role in Mediterranean trade.
  • 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_69d8278adc7c8190a9218d69bce3c4e6 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de622b89fc8190af08dab9e1976759 completed April 14, 2026, 3:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd2819bfec8190b555632338c53740 completed May 8, 2026, 12:02 a.m.
Created at: April 10, 2026, 1:07 a.m.