Triple

T16032994
Position Surface form Disambiguated ID Type / Status
Subject Qaryagin uezd E388893 entity
Predicate administrativeCenter P1474 FINISHED
Object Qaryagin E1190044 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: Qaryagin | Statement: [Qaryagin uezd, administrativeCenter, Qaryagin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Qaryagin
Context triple: [Qaryagin uezd, administrativeCenter, Qaryagin]
  • A. Qaryagin chosen
    Qaryagin is a town that historically served as the administrative center of the Qaryagin uezd in the Caucasus region.
  • B. Dugal
    Dugal is a masculine given name of Scottish origin, closely related to and often considered a variant of the name Dugald.
  • C. Quarazza
    Quarazza is a small hamlet in northern Italy associated with the alpine municipality of Macugnaga in the Piedmont region.
  • D. Drogo
    Drogo was an 11th-century Norman nobleman and military leader from the Hauteville family who became Count of Apulia in southern Italy.
  • E. Rykove
    Rykove is a former name of the industrial city now known as Yenakiieve in eastern Ukraine.
  • 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_69d86dada3808190825d5f80d72fbe88 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e183396a708190b53a589f6ac2c5bc completed April 17, 2026, 12:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffdbd1cafc81909125174eed475d55 completed May 10, 2026, 1:13 a.m.
Created at: April 10, 2026, 4:56 a.m.