Triple
T29694130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type I string theory |
E751295
|
entity |
| Predicate | hasMasslessOpenStringSector |
P199929
|
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, hasMasslessOpenStringSector, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMasslessOpenStringSector Context triple: [Type I string theory, hasMasslessOpenStringSector, yes]
-
A.
hasMasslessClosedStringSector
Indicates that a physical or theoretical model includes a sector of closed strings whose excitations are massless.
-
B.
hasMassTerm
Indicates that one entity is classified as a mass (uncountable) term associated with another entity.
-
C.
isNonSupersymmetric
Indicates that the entity does not exhibit or obey supersymmetry, i.e., it lacks a symmetry relating bosons and fermions.
-
D.
hasSupersymmetry
Indicates that a physical system, theory, or model exhibits supersymmetry, meaning there is a symmetry relating bosonic and fermionic degrees of freedom.
-
E.
hasRestMassUpperBound
Indicates that there is a specified maximum possible value for the rest mass of an entity.
- 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_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
| PDg | Predicate description generation | batch_69ff64b864f481909fcefc2b08595c89 |
completed | May 9, 2026, 4:45 p.m. |
Created at: April 28, 2026, 7:19 p.m.