Triple

T19337750
Position Surface form Disambiguated ID Type / Status
Subject Armenian Kingdom of Cilicia E483664 entity
Predicate formerCapital P3417 FINISHED
Object Vahka 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: Vahka | Statement: [Armenian Kingdom of Cilicia, formerCapital, Vahka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vahka
Context triple: [Armenian Kingdom of Cilicia, formerCapital, Vahka]
  • A. Vahka chosen
    Vahka was a medieval town that served as an early capital of the Armenian Kingdom of Cilicia.
  • B. Vahalis
    Vahalis is an ancient or historical name for the River Waal, a major distributary branch of the Rhine in the Netherlands.
  • C. Vauhallan
    Vauhallan is a small commune in the southern suburbs of Paris, located in the Essonne department in the Île-de-France region of northern France.
  • D. Vitasta
    Vitasta is the ancient Sanskrit name for the Jhelum River, a historically significant river of the Kashmir region frequently mentioned in Vedic and classical Indian texts.
  • E. Vahto
    Vahto is a small village and former municipality in Southwest Finland, now part of the town of Rusko.
  • 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_69d8e8d244f8819080eb1f3491300db2 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e61646e89081908c9f1d2cf557672c completed April 20, 2026, 12:04 p.m.
Created at: April 10, 2026, 1:33 p.m.