Triple

T23737884
Position Surface form Disambiguated ID Type / Status
Subject Type I supergravity E586585 entity
Predicate hasLocalSymmetry P26402 FINISHED
Object local supersymmetry 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: local supersymmetry | Statement: [Type I supergravity, hasLocalSymmetry, local supersymmetry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocalSymmetry
Context triple: [Type I supergravity, hasLocalSymmetry, local supersymmetry]
  • A. localSymmetry chosen
    Indicates that an entity exhibits symmetry within a localized region or subset of its structure, rather than across its entire extent.
  • B. symmetryOf
    Indicates that one entity is the symmetry counterpart or symmetric form of another entity, typically related by a specific symmetry operation or transformation.
  • C. symmetryInvolved
    Indicates that a relationship or action inherently involves symmetry, such as invariance under certain transformations or the presence of symmetric structure or behavior.
  • D. usesSymmetryGroup
    Indicates that one entity employs or is based on a particular symmetry group in its structure, behavior, or formulation.
  • E. hasSymmetryType
    Indicates that one entity possesses a specific kind or pattern of symmetry characterized or classified by the other 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_69e24907dc9c8190be074c9c96a0ec2d completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1bad356c88190ae29ce403145ee73 completed April 29, 2026, 8:01 a.m.
PD Predicate disambiguation batch_69f155f012808190a4b1cbc155558ade completed April 29, 2026, 12:50 a.m.
Created at: April 17, 2026, 7:11 p.m.