Triple

T1125196
Position Surface form Disambiguated ID Type / Status
Subject Haakon VII of Norway E24702 entity
Predicate acceptedThrone P25237 FINISHED
Object 1905-11-18 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: 1905-11-18 | Statement: [Haakon VII of Norway, acceptedThrone, 1905-11-18]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: acceptedThrone
Context triple: [Haakon VII of Norway, acceptedThrone, 1905-11-18]
  • A. lostThroneTo
    Indicates that one entity was previously in possession of a throne or rulership but was defeated or displaced so that another entity took that throne instead.
  • B. reignAs
    Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
  • C. wasCrowned
    Indicates that an entity formally received a crown or royal title in a ceremonial act of investiture.
  • D. heirOf
    Indicates that one entity is the legal or designated successor who inherits from another entity, typically upon that entity’s death or transfer of rights.
  • E. confirmedMonarch
    Indicates that an entity has been formally recognized and validated as the legitimate monarch, typically through an official confirmation process.
  • 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_69a4940712c88190aa244f3fc6070a65 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bc4bc21881909dcfe628f59f3e8c completed March 1, 2026, 10:23 p.m.
PD Predicate disambiguation batch_69a4bb4749ac8190b0fbddac2e9b2586 completed March 1, 2026, 10:18 p.m.
PDg Predicate description generation batch_69a4bc47fce48190825d3a877251f789 completed March 1, 2026, 10:23 p.m.
Created at: March 1, 2026, 7:44 p.m.