Triple

T25433547
Position Surface form Disambiguated ID Type / Status
Subject Kayles E637318 entity
Predicate decomposesInto P73433 FINISHED
Object disjoint subgames formed by separated blocks of pins 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: disjoint subgames formed by separated blocks of pins | Statement: [Kayles, decomposesInto, disjoint subgames formed by separated blocks of pins]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: decomposesInto
Context triple: [Kayles, decomposesInto, disjoint subgames formed by separated blocks of pins]
  • A. decomposesIn
    Indicates that one entity breaks down or separates into another entity or set of entities as its components or products.
  • B. hasDecomposition chosen
    Indicates that something can be broken down or separated into constituent parts, components, or simpler elements.
  • C. decompositionType
    Indicates the specific way in which a whole is broken down into its constituent parts or components.
  • D. decomposesAbove
    Indicates that one entity breaks down or disintegrates into parts or components that are located spatially above another entity.
  • E. yieldsDecomposition
    Indicates that one entity produces or results in a particular breakdown or decomposition of another entity.
  • 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_69e75db6c97081908178383fa632b193 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f6dd99f88190848a5bbee795aa17 completed May 2, 2026, 1:06 p.m.
PD Predicate disambiguation batch_69f4683b34748190818428489a226124 completed May 1, 2026, 8:45 a.m.
Created at: April 21, 2026, 1:59 p.m.