Triple

T20200607
Position Surface form Disambiguated ID Type / Status
Subject Greater Armenia E493206 entity
Predicate capital P234 FINISHED
Object Ani 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: Ani | Statement: [Greater Armenia, capital, Ani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ani
Context triple: [Greater Armenia, capital, Ani]
  • A. Ani chosen
    Ani was a medieval Armenian city renowned for its wealth, architectural splendor, and status as a major cultural and political center on the Silk Road.
  • B. Ani
    Ani is the Igbo earth goddess associated with morality, fertility, and the underworld in the Odinani traditional religion.
  • C. Ani
    Ani was an ancient Egyptian scribe whose funerary text, the Papyrus of Ani, is one of the most famous and complete illustrated versions of the Book of the Dead.
  • D. Ani
    Ani is an Etruscan sky and supreme deity, often associated with the heavens and divine authority in Etruscan religion.
  • E. Aani
    Aani is a month in the traditional Tamil calendar, typically falling around June–July in the Gregorian calendar and associated with various regional festivals and rituals.
  • 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_69da6269614c8190bb40475d9d477358 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66d8d01648190b1b3a6e03f0258d8 completed April 20, 2026, 6:16 p.m.
Created at: April 11, 2026, 11:37 p.m.