Triple
T29694190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M5-branes |
E751297
|
entity |
| Predicate | magneticDualOf |
P31338
|
FINISHED |
| Object | M2-branes |
—
|
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: M2-branes | Statement: [M5-branes, magneticDualOf, M2-branes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magneticDualOf Context triple: [M5-branes, magneticDualOf, M2-branes]
-
A.
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.
-
B.
magneticCharge
Indicates that an entity possesses a specified magnetic charge or is associated with a particular quantity or type of magnetic charge.
-
C.
magneticInteraction
Indicates a relationship in which entities exert forces or influences on each other due to their magnetic fields or magnetic properties.
-
D.
magneticField
Indicates the presence, strength, or configuration of a magnetic field associated with an entity or region.
-
E.
hasDualPolyhedron
Indicates that one polyhedron is the dual of another, meaning their vertices and faces correspond in an inverse, structure-preserving way.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672af46e48190b76e9298e7d23eef |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:19 p.m.