Triple

T16708833
Position Surface form Disambiguated ID Type / Status
Subject Anna Anka E406045 entity
Predicate familyName P18 FINISHED
Object Anka E652916 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: Anka | Statement: [Anna Anka, familyName, Anka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anka
Context triple: [Anna Anka, familyName, Anka]
  • A. Anka chosen
    Anka is a common diminutive form of the female given name Anna, used in several Slavic and Central European languages.
  • B. Anka-A
    Anka-A is an early variant of Turkey’s indigenous Anka unmanned aerial vehicle, designed primarily for medium-altitude, long-endurance surveillance and reconnaissance missions.
  • C. Anka-S
    Anka-S is a Turkish-made, satellite-controlled, medium-altitude long-endurance (MALE) unmanned aerial vehicle designed for extended surveillance and reconnaissance missions.
  • D. Anka-B
    Anka-B is an advanced variant of Turkey’s Anka unmanned aerial vehicle, featuring improved payload capacity, endurance, and surveillance capabilities for military reconnaissance and strike missions.
  • E. Ani
    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.
  • 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_69d8838db21081909589220fd71440a4 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e38650c3808190a561f22b169dc3ae completed April 18, 2026, 1:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a009d3adef081908692a4a86d7a0779 completed May 10, 2026, 2:59 p.m.
Created at: April 10, 2026, 5:20 a.m.