Triple

T35536551
Position Surface form Disambiguated ID Type / Status
Subject Moldavia E1026944 entity
Predicate transitionOfChanceryLanguageCentury P199797 FINISHED
Object 16th–17th centuries 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: 16th–17th centuries | Statement: [Moldavia, transitionOfChanceryLanguageCentury, 16th–17th centuries]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transitionOfChanceryLanguageCentury
Context triple: [Moldavia, transitionOfChanceryLanguageCentury, 16th–17th centuries]
  • A. centuryOfTranslation
    Indicates the century during which a translation of a work or text was produced.
  • B. statusIn15thCentury
    Indicates the status, condition, or standing that an entity had specifically during the 15th century.
  • C. historicalLanguageStage
    Indicates that one language variety represents an earlier historical stage or developmental phase of another language.
  • D. emergedByCentury
    Indicates that something came into existence, became prominent, or first appeared during a specified century.
  • E. medievalSeeTransferredTo
    Indicates that authority, ownership, or jurisdiction over a medieval ecclesiastical see was formally transferred from one holder or location to another.
  • F. None of above. chosen

Provenance (4 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_69f76dff7e508190b28ceeee770dce23 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69ff5803c02c81908b63067119f5e684 completed May 9, 2026, 3:51 p.m.
PD Predicate disambiguation batch_69ff576d8b308190b49a1e072a0ae661 completed May 9, 2026, 3:49 p.m.
PDg Predicate description generation batch_69ff58031bb081909fea985b16f69da4 completed May 9, 2026, 3:51 p.m.
Created at: May 3, 2026, 4:04 p.m.