Triple

T37769712
Position Surface form Disambiguated ID Type / Status
Subject Obersächsischer Reichskreis E941512 entity
Predicate hasNumberOfImperialCircles P199359 FINISHED
Object 1 of 10 Imperial Circles 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: 1 of 10 Imperial Circles | Statement: [Obersächsischer Reichskreis, hasNumberOfImperialCircles, 1 of 10 Imperial Circles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNumberOfImperialCircles
Context triple: [Obersächsischer Reichskreis, hasNumberOfImperialCircles, 1 of 10 Imperial Circles]
  • A. hasNumberOfImperialCities
    Indicates the relationship between an entity and the count of imperial cities associated with or contained within it.
  • B. hadImperialCircle
    Indicates that an entity was administratively organized within a specific Imperial Circle of the Holy Roman Empire.
  • C. hasRoyalCircle
    Indicates that an entity belongs to, is part of, or is associated with a royal or monarch’s inner circle or court.
  • D. hasImperialCultCenter
    Indicates that a place serves or served as a center for the worship and official cult of an emperor or imperial authority.
  • E. hasCircle
    Indicates that one entity possesses, contains, or includes a circle as part of its structure or composition.
  • 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_69f76ee3251881909bb4451aad50752b completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69ff2fbae9b48190847eefa1c227d43e completed May 9, 2026, 12:59 p.m.
PD Predicate disambiguation batch_69ff2f2218048190a32224a648182b5d completed May 9, 2026, 12:57 p.m.
PDg Predicate description generation batch_69ff2fb9e46c8190b36b3e0bc84f114c completed May 9, 2026, 12:59 p.m.
Created at: May 3, 2026, 4:19 p.m.