Triple

T10269829
Position Surface form Disambiguated ID Type / Status
Subject Chern–Simons theory E240804 entity
Predicate usesGaugeGroup P5369 FINISHED
Object compact Lie group 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: compact Lie group | Statement: [Chern–Simons theory, usesGaugeGroup, compact Lie group]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesGaugeGroup
Context triple: [Chern–Simons theory, usesGaugeGroup, compact Lie group]
  • A. gaugeGroup chosen
    Indicates a relationship where a physical or theoretical model is associated with the gauge group that defines its underlying symmetry structure.
  • B. gaugeType
    Indicates the specific kind or category of gauge associated with an entity or measurement.
  • C. usesGroup
    Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
  • D. standardGaugeWidth
    Indicates that something has the standard or officially accepted gauge width, typically referring to the distance between two rails in a railway track.
  • E. dominantGauge
    Indicates that one gauge in a system serves as the primary or controlling reference against which other gauges or measurements are compared or regulated.
  • 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_69d381a94c1881908fc38fc263d9b9c2 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d2872830819080fdfa816167d04c completed April 7, 2026, 9:46 a.m.
PD Predicate disambiguation batch_69d4d1ef6e6c81908a8ee52e4d28127b completed April 7, 2026, 9:44 a.m.
Created at: April 6, 2026, 11:35 a.m.