Triple

T9416504
Position Surface form Disambiguated ID Type / Status
Subject Wolfgang E227033 entity
Predicate hasHistoricalPopularity P27434 FINISHED
Object medieval Germany 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: medieval Germany | Statement: [Wolfgang, hasHistoricalPopularity, medieval Germany]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricalPopularity
Context triple: [Wolfgang, hasHistoricalPopularity, medieval Germany]
  • A. historicallyPopularIn chosen
    Indicates that something was notably popular or widely favored within a particular place or context during a past historical period.
  • B. historicallySoughtBy
    Indicates that one entity has been actively pursued, desired, or searched for by another entity in the past.
  • C. hasPopularityInfluencedBy
    Indicates that the popularity level of one entity is affected or shaped by another specified factor or entity.
  • D. hasEnduringPopularityOn
    Indicates that something continues to be widely liked, used, or appreciated on a particular platform, medium, or context over an extended period of time.
  • E. hasHistoricalCategory
    Indicates that something is associated with a particular historical classification, period, or type based on its past context or significance.
  • 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_69ca84359e7c819091148ba4b670e436 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd68c9917481909f793a2a9efb2a75 completed April 1, 2026, 6:49 p.m.
PD Predicate disambiguation batch_69cca54c37f88190bddccf28e5fe5c84 completed April 1, 2026, 4:55 a.m.
Created at: March 30, 2026, 7:48 p.m.