Triple
T20690419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SO(32) heterotic string theory |
E508535
|
entity |
| Predicate | dualityType |
P31338
|
FINISHED |
| Object | S-duality with Type I string theory |
—
|
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: S-duality with Type I string theory | Statement: [SO(32) heterotic string theory, dualityType, S-duality with Type I string theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dualityType Context triple: [SO(32) heterotic string theory, dualityType, S-duality with Type I string theory]
-
A.
haveDualityProperty
Indicates that an entity possesses a characteristic or state that inherently consists of two complementary, contrasting, or coexisting aspects.
-
B.
dualPair
chosen
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
-
C.
derivationType
Indicates the specific manner or process by which one entity is derived or obtained from another.
-
D.
denType
Indicates the specific kind or category of den associated with an entity.
-
E.
deltaType
Indicates a classification of the kind or category of change (difference) that has occurred between two related states or versions.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c10cb5588190acb88f2c82fc593a |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:08 p.m.