Triple

T23117149
Position Surface form Disambiguated ID Type / Status
Subject Duke of Edinburgh E576786 entity
Predicate canBeRecreated P150969 FINISHED
Object yes 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: yes | Statement: [Duke of Edinburgh, canBeRecreated, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canBeRecreated
Context triple: [Duke of Edinburgh, canBeRecreated, yes]
  • A. canBeReissued
    Indicates that something is eligible to be issued again, such as a document, license, or item that can be re-granted or re-produced after its initial issuance.
  • B. canRegenerate
    Indicates that an entity has the ability to regrow or restore lost or damaged parts of itself.
  • C. intendedToRecreate
    Indicates that one entity was created or performed with the purpose of reproducing, imitating, or restoring the characteristics, state, or effect of another entity.
  • D. supportsRecreationAt
    Indicates that one entity provides facilities, conditions, or resources that enable recreational activities to take place at a specified location.
  • E. canBeReconfigured
    Indicates that one entity has the capability to be altered, adjusted, or rearranged into a different configuration, typically under certain conditions or using specific methods.
  • 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_69e245f6c2e881909a228fdcfeb7c7d3 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18e4d095081908bad99fab6eaadd0 completed April 29, 2026, 4:51 a.m.
PD Predicate disambiguation batch_69ef89f020588190b43393e048e7eda3 completed April 27, 2026, 4:08 p.m.
PDg Predicate description generation batch_69ef9b7494f4819088ae59ea3d0ae8ab completed April 27, 2026, 5:23 p.m.
Created at: April 17, 2026, 3:59 p.m.