Triple

T13365184
Position Surface form Disambiguated ID Type / Status
Subject Battle of Cnidus E318920 entity
Predicate commander P1061 FINISHED
Object Conon E371767 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: Conon | Statement: [Battle of Cnidus, commander, Conon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Conon
Context triple: [Battle of Cnidus, commander, Conon]
  • A. Conon chosen
    Conon was a prominent 5th–4th century BCE Athenian admiral best known for rebuilding Athens’ naval power after its defeat in the Peloponnesian War.
  • B. Atarneus
    Atarneus was an ancient Greek city in the region of Mysia in western Asia Minor, known from classical sources and associated with figures such as Aristotle.
  • C. Aretus
    Aretus is a minor figure in Greek mythology known primarily as one of the sons of the wise Pylian king Nestor.
  • D. Pelineon
    Pelineon is a prominent mountain located on the Greek island of Chios in the Aegean Sea.
  • E. Lebbaeus
    Lebbaeus is an alternative name traditionally associated with the apostle Thaddaeus, one of the Twelve Apostles of Jesus in the New Testament.
  • 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_69d806b7bbac8190b85278c87fa7aff3 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69da628c71ac81908cfa36342077766e completed April 11, 2026, 3:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7267e9d608190b36f58a92d4a9964 completed May 3, 2026, 10:42 a.m.
Created at: April 9, 2026, 9:32 p.m.