Triple

T16451858
Position Surface form Disambiguated ID Type / Status
Subject Aternus E399570 entity
Predicate associatedWith P37 FINISHED
Object Marrucini E90816 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: Marrucini | Statement: [Aternus, associatedWith, Marrucini]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Marrucini
Context triple: [Aternus, associatedWith, Marrucini]
  • A. Marrucini chosen
    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.
  • B. 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.
  • C. Mucia
    Mucia was an ancient Roman noble family (gens) to which the patrician Mucia Tertia belonged.
  • D. Asculum
    Asculum was an important ancient city in central Italy, historically serving as the chief urban center of the Piceni people.
  • E. Maenza
    Maenza is a small historic town in the Lazio region of central Italy, known for its medieval architecture and hilltop setting.
  • 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_6a00679d15b08190b4e70e4337bff88d completed May 10, 2026, 11:10 a.m.
Created at: April 10, 2026, 5:10 a.m.