Triple

T29734349
Position Surface form Disambiguated ID Type / Status
Subject Type IIA string theory E752413 entity
Predicate hasBraneChargeQuantization P177339 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 IIA string theory, hasBraneChargeQuantization, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBraneChargeQuantization
Context triple: [Type IIA string theory, hasBraneChargeQuantization, yes]
  • A. hasElectricChargeQuantization
    Indicates that the electric charge of an entity can only take on discrete, quantized values rather than varying continuously.
  • B. magneticChargeQuantization
    Indicates that the magnetic charge of an entity can only take on discrete, quantized values rather than varying continuously.
  • C. hasChargeQuantizationLabeledBy
    Indicates that the charge quantization of one entity is specified or categorized using another entity as its label or classifier.
  • D. hasChargeConjugation
    Indicates that one entity is the charge-conjugated counterpart (particle vs. antiparticle form) of another entity.
  • E. magneticCharge
    Indicates that an entity possesses a specified magnetic charge or is associated with a particular quantity or type of magnetic charge.
  • 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_69f0d62a36a88190bf860f00da433ff8 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f6fb93224881908fc66fe76115fcdb completed May 3, 2026, 7:38 a.m.
PD Predicate disambiguation batch_69f6f969b4cc8190afb473a2d8b110bc completed May 3, 2026, 7:29 a.m.
PDg Predicate description generation batch_69f6fb17d5ec81909091e37e1ddbe577 completed May 3, 2026, 7:36 a.m.
Created at: April 28, 2026, 7:44 p.m.