Triple

T24784637
Position Surface form Disambiguated ID Type / Status
Subject Carrot Ironfoundersson E620085 entity
Predicate impliedRole P55539 FINISHED
Object rightful heir to the throne of Ankh-Morpork 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: rightful heir to the throne of Ankh-Morpork | Statement: [Carrot Ironfoundersson, impliedRole, rightful heir to the throne of Ankh-Morpork]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: impliedRole
Context triple: [Carrot Ironfoundersson, impliedRole, rightful heir to the throne of Ankh-Morpork]
  • A. impliesRole chosen
    Indicates that one role logically entails or gives rise to another role within a given context or system.
  • B. possibleRole
    Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
  • C. representedRole
    Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
  • D. providedRole
    Indicates that one entity has assigned or supplied a specific role or function to another entity.
  • E. perceivedRole
    Indicates the role or function that one entity is regarded or interpreted as having in relation to another, based on perception rather than objective status.
  • 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_69e2fabdbe8c8190adbb9434b8636cad completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f410d92ea08190b4a30f938fdd0b9c completed May 1, 2026, 2:32 a.m.
PD Predicate disambiguation batch_69f40ef612c88190ab2f3f08d4a92018 completed May 1, 2026, 2:24 a.m.
Created at: April 18, 2026, 4:45 a.m.