Triple

T6289299
Position Surface form Disambiguated ID Type / Status
Subject German Crown Prince Wilhelm E140974 entity
Predicate reignAsCrownPrinceTo P10353 FINISHED
Object 1918 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: 1918 | Statement: [German Crown Prince Wilhelm, reignAsCrownPrinceTo, 1918]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reignAsCrownPrinceTo
Context triple: [German Crown Prince Wilhelm, reignAsCrownPrinceTo, 1918]
  • A. predecessorAsCrownPrince
    Indicates that one entity previously held the position of crown prince immediately before another entity.
  • B. reignAs chosen
    Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
  • C. crownPrinceTo
    Indicates that one entity is the designated crown prince or heir apparent to another entity, typically a monarch or ruling position.
  • D. regentOf
    Indicates a relationship where one entity serves as the ruling authority or caretaker governing on behalf of another entity, typically during the latter’s minority, absence, or incapacity.
  • E. successorAsTitularKing
    Indicates that one entity becomes the next holder of a ceremonial or nominal kingship position previously held by another entity.
  • 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_69c008cd17c8819082b82d3fbeb68047 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0641a6ecc8190a63be0e3f0344a3f completed March 22, 2026, 9:50 p.m.
PD Predicate disambiguation batch_69c060df0d8881908215575862ef6831 completed March 22, 2026, 9:36 p.m.
Created at: March 22, 2026, 4:26 p.m.