Triple

T30555992
Position Surface form Disambiguated ID Type / Status
Subject Princess of Borovsk E777698 entity
Predicate historicallyDocumented P191878 FINISHED
Object yes 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: yes | Statement: [Princess of Borovsk, historicallyDocumented, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyDocumented
Context triple: [Princess of Borovsk, historicallyDocumented, yes]
  • A. historicallyDocumentedBy
    Indicates that information about an entity or event is recorded or attested in a specific historical document or source.
  • B. historicallyDescribedIn chosen
    Indicates that information about an entity has been recorded or characterized in a historical source or account.
  • C. historicallyIn
    Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
  • D. historicallyEncompassed
    Indicates that one entity previously included, covered, or contained another entity within its scope, extent, or boundaries during a past historical period.
  • E. historicalExistence
    Indicates that an entity actually existed at some point in real-world history, as opposed to being fictional, hypothetical, or mythological.
  • 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_69f2249e19108190a458ab446096bf22 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69feff70fbec8190b1ff5f943f29613e completed May 9, 2026, 9:33 a.m.
PD Predicate disambiguation batch_69fefbcd5b7881909cfe52b32f8a4301 completed May 9, 2026, 9:18 a.m.
Created at: April 29, 2026, 8:20 p.m.