Triple

T729854
Position Surface form Disambiguated ID Type / Status
Subject Peloponnese E14806 entity
Predicate contains P35 FINISHED
Object Corinth E61494 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: Corinth | Statement: [Peloponnese, contains, Corinth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Corinth
Context triple: [Peloponnese, contains, Corinth]
  • A. Corinth chosen
    Corinth was an influential ancient Greek city-state strategically located on the Isthmus of Corinth, known for its wealth, maritime trade, and cultural significance.
  • B. Pherae
    Pherae was an ancient Greek city in Thessaly known for its political influence and as the seat of the powerful tyrant Jason of Pherae.
  • C. Locri Epizephyrii
    Locri Epizephyrii was an important ancient Greek colony in southern Italy, renowned for its early legal code and cultural influence within Magna Graecia.
  • D. Sybaris
    Sybaris was an ancient Greek city in southern Italy famed for its immense wealth and legendary luxury.
  • E. Demetrias
    Demetrias was an ancient Greek city in the region of Thessaly, known as a significant Hellenistic and later Roman urban and naval center.
  • 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_69a4934d9930819099eed80096b0597d completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a5c290e481908497430a05dbfb90 completed March 1, 2026, 8:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69a76d742ef08190bb9405a1cde84eb1 completed March 3, 2026, 11:23 p.m.
Created at: March 1, 2026, 7:37 p.m.