Triple

T15428218
Position Surface form Disambiguated ID Type / Status
Subject Battle of Mantinea (418 BC) E369567 entity
Predicate belligerent P375 FINISHED
Object Argos E70939 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: Argos | Statement: [Battle of Mantinea (418 BC), belligerent, Argos]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Argos
Context triple: [Battle of Mantinea (418 BC), belligerent, Argos]
  • A. Argos
    Argos is the common nickname for the Toronto Argonauts, a professional Canadian Football League team based in Toronto.
  • B. Argos chosen
    Argos is one of the oldest continuously inhabited cities in Greece, located in the Peloponnese and historically significant as a major center of ancient Greek civilization.
  • C. Argos
    Argos is a major UK-based catalogue and online retailer known for offering a wide range of household goods, electronics, toys, and more through both physical stores and digital channels.
  • D. Argus
    Argus is an early distributed programming language known for pioneering concepts in fault-tolerant, distributed systems and influencing modern object-oriented and concurrent programming.
  • E. Argus
    Argus is a many-eyed giant from Greek mythology best known for his role as a vigilant guardian.
  • 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_69d85a1849f48190bf898068b2806fae completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ec31f4881908b26ff7c381d7bc9 completed April 16, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff219de0f88190a914bfee5dde32c9 completed May 9, 2026, 11:59 a.m.
Created at: April 10, 2026, 3:20 a.m.