Triple

T29694108
Position Surface form Disambiguated ID Type / Status
Subject Type I string theory E751295 entity
Predicate hasSpacetimeFermions P153490 FINISHED
Object yes 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: yes | Statement: [Type I string theory, hasSpacetimeFermions, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSpacetimeFermions
Context triple: [Type I string theory, hasSpacetimeFermions, yes]
  • A. hasFermions chosen
    Indicates that an entity possesses or is associated with one or more fermionic particles.
  • B. hasChiralFermions
    Indicates that the subject system or theory includes fermionic particles that exhibit chirality, meaning their left- and right-handed components transform differently under the relevant symmetry group.
  • C. hasFermionRepresentation
    Indicates that one entity can be represented or modeled in terms of fermionic degrees of freedom or a fermionic field theory.
  • D. hasFermionNumber
    Indicates that an entity is associated with a specific fermion number value, representing its net count of fermionic particles (fermions minus antifermions).
  • E. containsNonAbelianGaugeBosons
    Indicates that the entity includes gauge bosons associated with a non-Abelian (non-commutative) gauge symmetry group.
  • 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_69f0d625b09481909b0b69aea1e846c8 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69fb6fdc7eb081908ab8475efb38c430 completed May 6, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69fb5a986e588190b7a10892bd2ff44c completed May 6, 2026, 3:13 p.m.
Created at: April 28, 2026, 7:19 p.m.