Triple

T10200517
Position Surface form Disambiguated ID Type / Status
Subject Heir of Elendil E238870 entity
Predicate hasRightTo P39434 FINISHED
Object rule over the Reunited Kingdom 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: rule over the Reunited Kingdom | Statement: [Heir of Elendil, hasRightTo, rule over the Reunited Kingdom]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRightTo
Context triple: [Heir of Elendil, hasRightTo, rule over the Reunited Kingdom]
  • A. hasRightsOver chosen
    Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
  • B. hasLegalRight
    Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
  • C. hasAccessTo
    Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
  • D. hadRight
    Indicates that an entity possessed a legal or moral entitlement to perform an action, access something, or claim something in relation to another entity or situation.
  • E. hasAccessTowards
    Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or resource.
  • 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_69ca84e1ea088190b38162e43d4cfa8f completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdee3f3bac8190a63a81edffe7cda7 completed April 2, 2026, 4:19 a.m.
PD Predicate disambiguation batch_69cd7c8b7f348190a585daa70de4d4c8 completed April 1, 2026, 8:14 p.m.
Created at: March 30, 2026, 9:14 p.m.