Triple

T30337974
Position Surface form Disambiguated ID Type / Status
Subject Chess960 E771671 entity
Predicate openingName P178820 FINISHED
Object starting positions are often referred to by numeric codes 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: starting positions are often referred to by numeric codes | Statement: [Chess960, openingName, starting positions are often referred to by numeric codes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: openingName
Context triple: [Chess960, openingName, starting positions are often referred to by numeric codes]
  • A. openingAnswer
    Indicates that an entity provides an initial or first response in a dialogue, interaction, or sequence of answers.
  • B. openingDynamic
    Indicates that one entity initiates or begins another entity or process in a way that can change or vary over time or context.
  • C. openingStyle
    Indicates how something is initially presented, introduced, or begun in terms of manner, format, or approach.
  • D. openingOperator
    Indicates that an entity initiates or performs the action of opening another entity or resource.
  • E. openingInvocation
    Indicates the act of formally beginning an event, process, or sequence through an initiating statement, action, or call.
  • 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_69f2248aba24819095bb86480d55b23b completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f71422adac8190a5ceb32dcf820833 completed May 3, 2026, 9:23 a.m.
PD Predicate disambiguation batch_69f712764d2c819081b64b27e5de4a13 completed May 3, 2026, 9:16 a.m.
PDg Predicate description generation batch_69f71421e8d08190807ccfb15d0f0ddb completed May 3, 2026, 9:23 a.m.
Created at: April 29, 2026, 7:54 p.m.