Triple

T2282463
Position Surface form Disambiguated ID Type / Status
Subject Erebus E51310 entity
Predicate sibling P363 FINISHED
Object Pontus E77709 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: Pontus | Statement: [Erebus, sibling, Pontus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pontus
Context triple: [Erebus, sibling, Pontus]
  • A. Pontus chosen
    Pontus is a primordial Greek sea god who personifies the sea itself in ancient mythology.
  • B. Pontus
    Pontus was an ancient historical region along the southern coast of the Black Sea in what is now northeastern Turkey, known for its Hellenistic kingdom and strategic maritime position.
  • C. Taurica
    Taurica is the ancient name for the Crimean Peninsula, historically known as a Greek and later Roman-influenced region on the northern coast of the Black Sea.
  • D. Colchis
    Colchis was an ancient region on the eastern coast of the Black Sea, famed in Greek mythology as the destination of Jason and the Argonauts and the land of the Golden Fleece.
  • E. Illyrius
    Illyrius is a figure in Greek mythology regarded as the eponymous ancestor of the Illyrian peoples.
  • 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_69a88b08e4308190bdac9aebcca1c91a completed March 4, 2026, 7:42 p.m.
NER Named-entity recognition batch_69abc21d6d748190980128c1bc5b9621 completed March 7, 2026, 6:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae71e7b44c8190ab647646352b71b7 completed March 9, 2026, 7:08 a.m.
Created at: March 4, 2026, 7:48 p.m.