Triple
T29694177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M2-branes |
E751296
|
entity |
| Predicate | hasMagneticDualObject |
P199951
|
FINISHED |
| Object | M5-branes |
—
|
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: M5-branes | Statement: [M2-branes, hasMagneticDualObject, M5-branes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagneticDualObject Context triple: [M2-branes, hasMagneticDualObject, M5-branes]
-
A.
usesMagnetType
Indicates that one entity employs or operates with a specific type of magnet in its function or configuration.
-
B.
hasMagSafePort
Indicates that one entity is equipped with or includes a MagSafe charging or power connector port.
-
C.
hasMagneticMoment
Indicates that an entity possesses a magnetic moment, characterizing the strength and orientation of its magnetism.
-
D.
hasDualSpace
Indicates that one mathematical space is the dual space consisting of all linear functionals defined on another space.
-
E.
hasMagnetStatus
Indicates that an entity possesses a specific magnet-related state or designation within a given context.
- 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_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
| PDg | Predicate description generation | batch_69ff659717708190bb56714d1b261063 |
completed | May 9, 2026, 4:49 p.m. |
Created at: April 28, 2026, 7:19 p.m.