Triple

T21807103
Position Surface form Disambiguated ID Type / Status
Subject Siege of Agrigentum E538377 entity
Predicate location P40 FINISHED
Object Agrigentum NE NERFINISHED

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: Agrigentum | Statement: [Siege of Agrigentum, location, Agrigentum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Agrigentum
Context triple: [Siege of Agrigentum, location, Agrigentum]
  • A. Akragas chosen
    Akragas was an important ancient Greek city on the southern coast of Sicily, renowned for its wealth, powerful status, and monumental temples.
  • B. Leontini
    Leontini was an ancient Greek city in eastern Sicily, known as a Chalcidian colony and a frequent player in the island’s classical-era conflicts.
  • C. Gela
    Gela is a river in southern Sicily, Italy, that flows into the Mediterranean Sea near the city of Gela.
  • D. Gela
    Gela is a mountain village in the Rhodope Mountains of southern Bulgaria, known for its scenic landscapes and traditional Bulgarian culture.
  • E. Gela
    Gela is an Oceanic language spoken primarily in the Solomon Islands, particularly on Nggela (Florida) Islands in Central Province.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c473f0f8819086c9d1b4a143bd67 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f07803b4888190af06bf7a90198f60 completed April 28, 2026, 9:04 a.m.
Created at: April 16, 2026, 6:53 p.m.