Triple

T29694114
Position Surface form Disambiguated ID Type / Status
Subject Type I string theory E751295 entity
Predicate hasTachyonInUnstableBackgrounds P172399 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, hasTachyonInUnstableBackgrounds, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTachyonInUnstableBackgrounds
Context triple: [Type I string theory, hasTachyonInUnstableBackgrounds, yes]
  • A. hasBackground
    Indicates that an entity possesses or is associated with a particular background, such as context, setting, or prior circumstances.
  • B. hasBackgroundClutter
    Indicates that the scene or image contains additional, potentially distracting elements in the background around the main subject.
  • C. hasStageBackground
    Indicates that one entity serves as the stage background for another entity in a performance or scene.
  • D. hasBackgroundSample
    Indicates that an entity is associated with or linked to a corresponding background sample used for comparison or reference.
  • E. hasNotableHostBackground
    Indicates that the host of an event, show, or program has a background or profile that is considered particularly significant, distinguished, or noteworthy.
  • 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_69f0d625b09481909b0b69aea1e846c8 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f6abe15d5c81909ccf4ce37f78bc43 completed May 3, 2026, 1:58 a.m.
PD Predicate disambiguation batch_69f6aa1c555081908787dbf76147f180 completed May 3, 2026, 1:51 a.m.
PDg Predicate description generation batch_69f6aaf31a548190b2f792ff4b8c002a completed May 3, 2026, 1:54 a.m.
Created at: April 28, 2026, 7:19 p.m.