Triple

T18774433
Position Surface form Disambiguated ID Type / Status
Subject Neikea E459098 entity
Predicate opposedTo P437 FINISHED
Object Homonoia NE NERFINISHED

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: Homonoia | Statement: [Neikea, opposedTo, Homonoia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Homonoia
Context triple: [Neikea, opposedTo, Homonoia]
  • A. Homonoia chosen
    Homonoia is the ancient Greek personification and goddess of unity, concord, and social harmony within the community.
  • B. Ἁρμονία
    Ἁρμονία is the Greek goddess personifying harmony and concord, traditionally known as the daughter of Ares and Aphrodite and the wife of Cadmus.
  • C. Phoebastria
    Phoebastria is a genus of large seabirds in the albatross family, comprising several North Pacific albatross species.
  • D. Naissos
    Naissos is the ancient name of the city of Niš, a historically significant urban center in present-day Serbia known since Roman times.
  • E. Omonoia
    Omonoia is a central and historically significant square and transport hub in Athens, Greece, known for its busy urban atmosphere and commercial activity.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d395dba0819087568404508590cb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5933888408190a21f9ac5b360d1eb completed April 20, 2026, 2:45 a.m.
Created at: April 10, 2026, 11:52 a.m.