Triple

T19402942
Position Surface form Disambiguated ID Type / Status
Subject Kamarina E485373 entity
Predicate hasNearbyArchaeologicalSite P14422 FINISHED
Object Cassope 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: Cassope | Statement: [Kamarina, hasNearbyArchaeologicalSite, Cassope]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cassope
Context triple: [Kamarina, hasNearbyArchaeologicalSite, Cassope]
  • A. Cassope chosen
    Cassope is an ancient Greek city in the region of Epirus, known for its well-preserved Hellenistic urban remains and panoramic hilltop location.
  • B. Korissos
    Korissos is a locality in Greece, also known by the alternative name Korissia.
  • C. Cassiphonē
    Cassiphonē is a minor figure in Greek mythology, known primarily as a name variant of Cassiphone mentioned in some mythological genealogies.
  • D. Almyros
    Almyros is a coastal town in central Greece, near the Pagasetic Gulf, known for its agricultural production and proximity to both seaside and mountainous landscapes.
  • E. Ousanas
    Ousanas was a king of the ancient Kingdom of Aksum in what is now Ethiopia, known from inscriptions and coinage as an early Christian-era ruler preceding King Ezana.
  • 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_69d8e8d5162481909db12435d9535c1a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e62577f808819099e74feab82b34a4 completed April 20, 2026, 1:09 p.m.
Created at: April 10, 2026, 1:36 p.m.