Triple

T6145780
Position Surface form Disambiguated ID Type / Status
Subject Strabo E137072 entity
Predicate birthPlace P1 FINISHED
Object Amaseia E325073 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: Amaseia | Statement: [Strabo, birthPlace, Amaseia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amaseia
Context triple: [Strabo, birthPlace, Amaseia]
  • A. Amaseia chosen
    Amaseia was an ancient city in northern Anatolia that served as the early capital of the Kingdom of Pontus and an important regional political and cultural center.
  • B. Ambracia
    Ambracia was an ancient Greek city in Epirus that became an important regional center and later the capital of King Pyrrhus.
  • C. Taurisium
    Taurisium is an ancient fortified settlement in present-day North Macedonia, traditionally regarded as the birthplace of the Byzantine emperor Justinian I.
  • D. Selinus
    Selinus was an ancient Greek city on the southwest coast of Sicily, notable for its grand Doric temples and strategic position in the western Greek colonial world.
  • E. Anazarbus
    Anazarbus was an important ancient city in the region of Cilicia, in what is now southern Turkey, known for its strategic location and impressive fortifications.
  • 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_69c008a2c6308190a56519b22d55d083 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c05cdd2dc0819080a4adf0cead3603 completed March 22, 2026, 9:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69c135fe8ae48190bfb20c335c7d32be completed March 23, 2026, 12:45 p.m.
Created at: March 22, 2026, 4:16 p.m.