Triple

T4176933
Position Surface form Disambiguated ID Type / Status
Subject King Shahryar E86498 entity
Predicate resolutionOfArc P54230 FINISHED
Object abandons executions 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: abandons executions | Statement: [King Shahryar, resolutionOfArc, abandons executions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: resolutionOfArc
Context triple: [King Shahryar, resolutionOfArc, abandons executions]
  • A. resolution
    Indicates the act of formally deciding, settling, or expressing a determined stance on an issue, often through an official decision or statement.
  • B. resolutionClass
    Indicates the category or type of resolution applied to address or conclude a particular issue, conflict, or process.
  • C. resolutionType
    Indicates the specific manner or category by which an issue, event, or conflict is resolved or brought to a conclusion.
  • D. resolvedIn
    Indicates that an issue, conflict, or process is brought to a conclusion or solution within a specified context, medium, or timeframe.
  • E. hasResolution
    Indicates that one entity possesses, specifies, or is associated with a particular level or type of resolution (such as detail, clarity, or granularity) in relation to another entity.
  • 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_69aed93de98c8190ad838ce507b77c8a completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af07078cb081909f64326b12522410 completed March 9, 2026, 5:44 p.m.
PD Predicate disambiguation batch_69af019155448190b19868583272513f completed March 9, 2026, 5:21 p.m.
PDg Predicate description generation batch_69af07059d288190a1ea79449414fbce completed March 9, 2026, 5:44 p.m.
Created at: March 9, 2026, 3:45 p.m.