Triple

T28082148
Position Surface form Disambiguated ID Type / Status
Subject Khokhlov E709709 entity
Predicate heritageIndication P17327 FINISHED
Object Slavic heritage LITERAL 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: Slavic heritage | Statement: [Khokhlov, heritageIndication, Slavic heritage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heritageIndication
Context triple: [Khokhlov, heritageIndication, Slavic heritage]
  • A. heritageValue
    Indicates that something possesses cultural, historical, or traditional significance that is valued and preserved as heritage.
  • B. heritageStatus
    Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
  • C. heritageType
    Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
  • D. heritageReference chosen
    Indicates that one entity serves as a cultural, historical, or heritage-related reference or source for another entity.
  • E. heritageSystem
    Indicates that one entity functions as a heritage or legacy system in relation to another, typically as an older or foundational technological system that the other depends on, interfaces with, or is intended to replace.
  • F. None of above.

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_69ef9b7037f0819095bb90eaccbcaf32 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f6e6029a10819098ff21f58079e70e completed May 3, 2026, 6:06 a.m.
PD Predicate disambiguation batch_69f6e3d5e8188190b1e1c2e5d1b77031 completed May 3, 2026, 5:57 a.m.
Created at: April 27, 2026, 8:52 p.m.