Triple

T12116873
Position Surface form Disambiguated ID Type / Status
Subject ЗА ОБОРОНУ ЛЕНИНГРАДА E288586 entity
Predicate instanceOf P0 FINISHED
Object Russian inscription C30944 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: Russian inscription
Context triple: [ЗА ОБОРОНУ ЛЕНИНГРАДА, instanceOf, Russian inscription]
  • A. Latin inscription
    A Latin inscription is a text carved, engraved, or otherwise permanently marked in the Latin language on durable materials such as stone, metal, or pottery, typically serving commemorative, dedicatory, legal, or informational purposes.
  • B. religious inscription
    A religious inscription is a text carved, written, or otherwise permanently recorded on a durable surface that conveys sacred messages, prayers, dedications, or doctrinal statements associated with a particular faith tradition.
  • C. ancient Greek inscription
    An ancient Greek inscription is a text carved, painted, or otherwise permanently marked on durable materials such as stone, metal, or pottery in the Greek language, typically serving public, religious, legal, or commemorative purposes in antiquity.
  • D. Georgian inscription
    A Georgian inscription is a text carved, written, or otherwise rendered in the Georgian script, typically found on monuments, buildings, artifacts, or manuscripts, conveying historical, religious, or commemorative information.
  • E. Etruscan inscription
    An Etruscan inscription is a text written in the ancient Etruscan language, typically carved or painted on durable materials such as stone, metal, or pottery, providing evidence of the culture, religion, and daily life of the Etruscan civilization.
  • F. None of above. chosen

Provenance (1 batch)

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_69d6ab4a5c448190a110d1273314b21a completed April 8, 2026, 7:23 p.m.
Created at: April 8, 2026, 9:49 p.m.