Triple

T36870575
Position Surface form Disambiguated ID Type / Status
Subject BPST instanton E911211 entity
Predicate belongsToTopologicalSector P201482 FINISHED
Object winding number 1 sector 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: winding number 1 sector | Statement: [BPST instanton, belongsToTopologicalSector, winding number 1 sector]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: belongsToTopologicalSector
Context triple: [BPST instanton, belongsToTopologicalSector, winding number 1 sector]
  • A. sectorizationContext
    Indicates the contextual framework or conditions under which a system, area, or domain is divided into distinct sectors or segments.
  • B. belongsToSubsector
    Indicates that one entity is part of, or classified within, a more specific subsector of a broader sector or industry.
  • C. hasSectorization
    Indicates that one entity is divided into, assigned to, or associated with specific sectors defined by another entity.
  • D. hasTopographicalRole
    Indicates that an entity serves a specific functional or positional role within a topographical or spatial context.
  • E. usesTopology
    Indicates that one entity employs, is based on, or operates according to a particular topology defined or provided by 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_69f76e80f6f0819091cba8e19b269615 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fff9b126b4819085a4cf8791d388d1 completed May 10, 2026, 3:21 a.m.
PD Predicate disambiguation batch_69fff8f913a881908d3b7e490d92631f completed May 10, 2026, 3:18 a.m.
PDg Predicate description generation batch_69fff9b0338c8190a24ed0b5dc9784b2 completed May 10, 2026, 3:21 a.m.
Created at: May 3, 2026, 4:13 p.m.