Triple
T29734331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type IIA string theory |
E752413
|
entity |
| Predicate | isRelatedByDualityTo |
P31338
|
FINISHED |
| Object | M-theory |
—
|
NE NERFINISHED |
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: M-theory | Statement: [Type IIA string theory, isRelatedByDualityTo, M-theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRelatedByDualityTo Context triple: [Type IIA string theory, isRelatedByDualityTo, M-theory]
-
A.
hasTdualityPartner
Indicates that one entity is related to another as its T-dual counterpart, typically under T-duality transformations in string theory.
-
B.
haveDualityProperty
Indicates that an entity possesses a characteristic or state that inherently consists of two complementary, contrasting, or coexisting aspects.
-
C.
isInverseOf
Indicates that one relation reverses the direction of another, so that if the original relates A to B, its inverse relates B to A.
-
D.
allyRelation
Indicates a cooperative, supportive relationship in which the entities act as allies toward shared or aligned goals.
-
E.
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.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 7:44 p.m.